Add step to generate constraints in Python SDK release process

[kaxil]

I have been manually generating constraints when I release - https://github.com/astronomer/astro-sdk/releases/tag/constraints-1.3.3

so that Cloud IDE can use it for installation. Example https://github.com/astronomer/astro/pull/7339

We should document this process in https://github.com/astronomer/astro-sdk/blob/main/python-sdk/docs/development/RELEASE.md

[kaxil]

fyi @pankajastro @utkarsharma2 @phanikumv @sunank200

[kaxil]

The way I do it manually right now is:

1. First I create a new branch of the last constraints branch. Example ❯ git branch constraints-1-4 constraints-1-3
2. Checkout that branch git checkout constraints-1-4
3. Find the Github action CI job that ran when you tagged the release and which published the artifact. In your case it was https://github.com/astronomer/astro-sdk/actions/runs/3901647585
4. I download all the constraints file at the bottom of that GH page as shown in the screenshot below
5. I remove old files: ❯ rm *.txt and unzip *.zip all the files and then delete zips rm *.zip
6. Then rename them: ❯ for f in constraints*; do mv "$f" "$f.txt"; done
7. git add const* && ❯ git commit -m "Update constraints for Astro SDK 1.4.0" --no-verify && git push origin constraints-1-4 && git tag constraints-1.4.0 && git push origin constraints-1.4.0