This is cool you do it :). Great to get someone else looking at it "seriously" :)

Two comments:

1. this PR should be continuously rebased until we release the previous wave, we then remove those providers that will need a new version and we will do new RCs from that

2. after releasing and tagging current providers you will need to rebase this one to main, and run breeze release-management prepare-provider-docuementation cncf.kubernetes jdbc asana google grpc yandex (and all others we touched). This does the following:

• it asks you for each changed providers to classify changes that were done in the meantime - in some cases this will be "doc only change" but in some others we will need to bump/change a new version of the provider in question
• it will regenerate COMMITS.rst
• it will automatically append the changes since last released that were merged in main to CHANGELOGs - this way any changes that were merged between, will not be forgotten - you will get them regenerted in a new section with the right comment and before adding/committing changes we should adjust CHANGELOG

This is the process I've been following so far and it works very well IMHO.

Incorporated in #27774