ci(release): add a catch-all category to the release notes template

[MateoLostanlen]

• .github/release.yml defined five label-based categories and no catch-all, so GitHub dropped every PR matching none of them. Since engine PRs carry no labels, the generated notes came out empty, as in v1.0.18.
• Adds - title: Other changes / labels: ["*"] after the specific categories, which is what pyro-api does. Existing categories keep their precedence.
• Config only, effective on the next release cut from develop.

Checked with GitHub's own generator over the same range (v1.0.17..HEAD): empty body with the config on develop, PRs listed under "Other changes" with the config on this branch.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.11%. Comparing base (968284f) to head (cab1cee).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #409      +/-   ##
===========================================
+ Coverage    78.83%   79.11%   +0.28%     
===========================================
  Files            6        6              
  Lines          841      838       -3     
===========================================
  Hits           663      663              
+ Misses         178      175       -3     

Flag	Coverage Δ
unittests	79.11% <ø> (+0.28%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.