Work on 3.1 release

Release 3.1.0 is scheduled for January 2026

### Detailed info:
* https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md

### Kick-off:
no kick off meeting

### Release branches:
* https://github.com/asyncapi/spec/tree/master based on https://github.com/asyncapi/spec/pull/1109
* https://github.com/asyncapi/spec-json-schemas/tree/feat/ros2-bindings
* https://github.com/asyncapi/parser-js/tree/maste - no PR or branch, there will only be bump of new `@asyncapi/specs` release
* https://github.com/asyncapi/bindings/tree/master based on https://github.com/asyncapi/bindings/pull/270

### Release notes:

https://github.com/asyncapi/website/pull/5034

### Progress:

tbd

- [x] Create release branches - not all repos need a release branch
- ~[ ] spec~
- [x] spec-json-schemas
- ~[ ] parser-js~
- ~[ ] bindings~
- [x] Update release branches with new versions
- ~[ ] spec~
- [x] spec-json-schemas
- ~[ ] parser-js~
- [x] Update default branches with release branch name
- ~[ ] spec~
- [x] spec-json-schemas
- ~[ ] parser-js~
- [x] Create draft release notes
- [x] Update release branches from forks
- ~[ ] spec~
- [x] spec-json-schemas
- ~[ ] parser-js~
- [x] Notify community about release branches
- [x] Check for potential release contributions
- [x] Draft announcement blog post for new features and changes
- [x] Write release notes for new features and changes
- [x] Prepare pull requests to merge release branches into master
- ~[ ] spec~
- [x] spec-json-schemas
- ~[ ] parser-js~
- [x] Notify tsc_members about upcoming release
- [x] Merge release branches into master
- [ ] spec
- [x] spec-json-schemas
- [x] parser-js
- [x] Write release notes for the releases on Github
- [x] Create releases on Github
- [x] spec
- [x] spec-json-schemas
- [x] parser-js
- [ ] Update RELEASE_PROCESS doc with any changes

### Cleanup tasks after the release

tbd

- [ ] release process improvements

Start by reading RELEASE_PROCESS.md and the linked release notes PR, then compare the completed checklist with the remaining release work across the referenced repositories. Done means updating RELEASE_PROCESS.md with process changes and completing the remaining release cleanup tasks.

Written by the indexing model from the issue text.