FIX: Add pre-commit Blacken-docs hooks

[Revathyvenugopal162]

• Part of STYLE replace flake8-rst with something maintained #46865 (Replace xxxx with the GitHub issue number)
• Tests added and passed if fixing a bug or adding a new feature
• All code checks passed.
• Added type annotations to new arguments/methods/functions.
• Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature.

This PR adds the configuration for the blacken-docs hook to the project's .pre-commit-config.yaml file. The blacken-docs hook applies the Black code formatter to reStructuredText (reST) files.

To accommodate potential parsing errors encountered with certain code blocks, the --skip-errors argument is included in the hook configuration. This argument instructs blacken-docs to skip errors and continue processing other files and blocks.

By including the blacken-docs hook with error skipping, we can ensure consistent formatting of reST files while allowing exceptions for code blocks that may contain unsupported syntax.

Please review this PR and provide any feedback or suggestions for improvement.

@noatamir @phofl SciPy Sprint 2023

[rhshadrach]

Thanks for the PR! By putting partially closes #... in the OP, I believe merging this will automatically close the corresponding issue. This is because GitHub does not pickup on the "partially". Instead, I recommend "Part of #..."

[rhshadrach]

I believe this is what's causing the CI to fail. With nbsphinx, multiple blank lines will generate a warning causing our docs build to fail (docs are still built successfully though). Not sure if there is a good way to handle this.

https://github.com/pandas-dev/pandas/actions/runs/5563179982/jobs/10161969704?pr=54137#step:6:44

[github-actions]

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

[mroeschke]

Thanks for the pull request, but it appears to have gone stale. If interested in continuing, please merge in the main branch, address any review comments and/or failing tests, and we can reopen.