ci: improve release workflow

[reubenmiller]

Proposed changes

Improve release workflow by automating more steps

• Use PAT when creating a PR (so that github actions checks will also be run)
• Trigger tedge-docs workflow on tags to create a new doc snapshot PR
• Create a tag when detecting a change in the Cargo.toml package.version (result of triggering the hosted-post-merge_version_update.yml workflow)

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

#2704

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s)
• I ran cargo fmt as mentioned in CODING_GUIDELINES
• I used cargo clippy as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (dcd0976) 76.9% compared to head (b76bad8) 76.9%.
Report is 1 commits behind head on main.

Additional details and impacted files

see 3 files with indirect coverage changes