BUG: Set check_exact to true if dtype is int
- [x] closes #55882 
- [x] [Tests added and passed]
- [x] All [code checks passed]
- [ ] Added [type annotations]
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

 @MarcoGorelli not sure where to add test cases for the change.
 
 Edit: Got it (pandas/tests/util/test_assert_frame_equal.py)  Well I'm relieved that CI is still green 😄 Can you update the docs for this method to note that `rtol`, `atol` and `check_exact` don't take effect for int dtype?

Regarding the check - not totally sure about the check, will take a closer look next week Sure. Updated the documentation. Added note under `check_exact`. Since we are setting it to True in case of int dtype. Also, documentation for `rtol` and `atol` states it is applicable only when check_exact is False so I assumed that it is sufficient to add note under `check_exact` I think it should always be exact, except for floats?

You should also check for extensions arrays, and include a whatsnew

I've added a commit anyway, hope it's ok - do the changes look alright to you? Yeah, make sense.

Some testcases are failing in some builds. Is that alright? Looks like another bug was hiding because of the check_exact default 😄  https://github.com/pandas-dev/pandas/issues/56136

For now let's xfail the relevant test Sure Marco Thanks @parthi-siva and @MarcoGorelli  > Looks like another bug was hiding because of the check_exact default 😄 #56136
> 
> For now let's xfail the relevant test

@jorisvandenbossche yeah.. there was another issues because of this 