chore: add release documentation

[jonas-jonas]

Related Issue or Design Document

Checklist

• I have read the contributing guidelines and signed the CLA.
• I have referenced an issue containing the design document if my change introduces a new feature.
• I have read the security policy.
• I confirm that this pull request does not address a security vulnerability.
  If this pull request addresses a security vulnerability,
  I confirm that I got approval (please contact security@ory.sh) from the maintainers to push the changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have added the necessary documentation within the code base (if appropriate).

Further comments

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 50.16%. Comparing base (f3fad4d) to head (5039213).
Report is 51 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #379      +/-   ##
==========================================
+ Coverage   42.43%   50.16%   +7.73%     
==========================================
  Files         136      140       +4     
  Lines        2008     2139     +131     
  Branches      288      318      +30     
==========================================
+ Hits          852     1073     +221     
+ Misses       1149     1053      -96     
- Partials        7       13       +6     

Components	Coverage Δ
@ory/elements-react	46.89% <36.72%> (+10.10%)	⬆️
@ory/nextjs	64.33% <74.24%> (-1.65%)	⬇️

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.