Adding new flags to have a sanity check before bumping version in provider-documentation

[poorvirohidekar]

closes: #47267

This PR adds support to introduce

1. 3 new flags --allow-already-released , --version-suffix-for-pypi, --version-suffix-for-local for the preparation of provider-documentation. This is similar to the implementation done for provider-packages to run a sanity check before bumping the version if present in
   a) local tags
   b) remote tags

2. Also add a sanity check if the version is already present in the changelog.rst for a given provider.

Testing:

1. To exit if the version already exists in the changelog.rst for a given provider. Simulate a scenario where we need to bump the version by running command breeze release-management prepare-provider-documentation amazon but version 5.1.0 already exists in the changelog

3. Add a local tag for airbyte provider version -> 5.0.1 then run the breeze release management prepare-provider-documentation airbyte, since this already exists it should skip generating any documentation

4. After step 2, run breeze release-management prepare-provider-documentation airbyte --allow-already-released
   this should allow the document creation

5. breeze release-management prepare-provider-documentation airbyte --version-suffix-for-pypi 5.0.0

Even if an older version is given, it will pick up the version marked for release

Similarly for the command --version--suffix-for-pypi.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[poorvirohidekar]

cc: @eladkal @potiuk @amoghrajesh

[bugraoz93]

Could you please add test cases for these newly added flags and methods? You can find the tests under dev/breeze/tests

[poorvirohidekar]

Hi can i please get a review on this PR?

Cc : @potiuk

[eladkal]

Will review today thanks for reminder

[potiuk]

That looks generally good - but should be rebased and I think some documentation in release management section possibly should be updated about it. Sorry for delay - but Airflow 3 and refactoring is eating all the time .

[eladkal]

This will exit the process?
If detected we should show the message and let release manager fix it, once fixed it should continue from the same place. Basically, don't exit the process just redo the command for this provider after release manager fixed the issue.
Looking for something like:

Version {v} already exists in CHANGELOG. Fix manually before proceeding.
Click Y for redo this provider after fix, S to skip this provider, Q to exist the process.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.