Restrict clipping of DataFrame.corr only when cov=False
 Closes #61154 `DataFrame.corr` was clipped between `-1` and `1` to handle numerical precision errors. However, this was done regardless of whether `cov` equals `True` or `False`, and should instead only be done when `cov=False`.

- [x] closes #61154 (Replace xxxx with the GitHub issue number)
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

@mroeschke here is my pull request for fixing the `dataframe.corr` issue. Thanks! Thanks! Would you be able to add new unit test that covers this? It seems like we didn't have one that hit this edge case previously.

I think no release note is necessary, since the original one made clear it's only for `corr`. Thanks @j-hendricks 