Create Release PR workflow

[lucacome]

Proposed changes

Problem: Manually updating the old tag is boring and error prone

Solution: Automate the process and automatically open a PR for the
release

Closes #1418

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes

If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

NONE

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.16%. Comparing base (45a4085) to head (263c23d).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1732      +/-   ##
==========================================
+ Coverage   85.62%   86.16%   +0.54%     
==========================================
  Files          86       87       +1     
  Lines        5306     5515     +209     
  Branches        0       52      +52     
==========================================
+ Hits         4543     4752     +209     
  Misses        717      717              
  Partials       46       46              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.