fix(ci): specify semantic release version that is compatible with node 18

[brian-smith-tcril]

Description:

semantic-release version 23 includes the following breaking change:

• support for node v18 has been dropped and the minimum for v20 is now v20.8.1

This pins the release workflow to version 22 until we move away from node 18.

Merge checklist:

• Consider running your code modifications in the included example app within frontend-platform. This can be done by running npm start and opening http://localhost:8080.
• Consider testing your code modifications in another local micro-frontend using local aliases configured via the module.config.js file in frontend-build.
• Verify your commit title/body conforms to the conventional commits format (e.g., fix, feat) and is appropriate for your code change. Consider whether your code is a breaking change, and modify your commit accordingly.

Post merge:

• After the build finishes for the merged commit, verify the new release has been pushed to NPM.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (88fd140) 83.50% compared to head (da9300b) 83.50%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #639   +/-   ##
=======================================
  Coverage   83.50%   83.50%           
=======================================
  Files          40       40           
  Lines        1073     1073           
  Branches      197      197           
=======================================
  Hits          896      896           
  Misses        165      165           
  Partials       12       12           

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

[arbrandes]

Nice catch! Approved.