Address Sphinx Warnings in Docs Warnings Presubmit

[ohmayr]

Once we disable the setting to treat warnings as errors as part of the performance initiative, we need to investigate which warnings need to be addressed and whether they need a fix upstream. We will also be getting rid of https://github.com/googleapis/google-cloud-python/blob/main/.librarian/generator-input/client-post-processing/doc-formatting.yaml . If we find that any of these replacements are actually making docs more readable, we should make sure to surface them and make a plan to address it

[abdulwahabahmedkhanyusufzai]

Hi @ohmayr, I’m interested in helping with this documentation cleanup. Since you’re planning to deprecate the doc-formatting.yaml approach, I can help investigate the Sphinx warnings currently being suppressed and work on fixing them at the source in the docstrings.

Could you point me to the latest logs or a specific library where these warnings are most prevalent? Also, are there any specific 'upstream' repositories where you've already identified that fixes need to be pushed, or should I start with a local audit of the google-cloud-python monorepo?

[parthea]

Closing as obsolete as we're no longer treating docs warnings as errors as of #16627