ci: update .releaserc to publish from appropriate branches

[brian-smith-tcril]

Description

see #3272

Include a description of your changes here, along with a link to any relevant Jira tickets and/or Github issues.

Deploy Preview

Include a direct link to your changes in this PR's deploy preview here (e.g., a specific component page).

Merge Checklist

• If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
• Does your change adhere to the documented style conventions?
• Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
• Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
• Were your changes tested in the example app?
• Is there adequate test coverage for your changes?
• Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please request an a11y review for the PR in the #wg-paragon Open edX Slack channel.

Post-merge Checklist

• Verify your changes were released to NPM at the expected version.
• If you'd like, share your contribution in #show-and-tell.
• 🎉 🙌 Celebrate! Thanks for your contribution.

[netlify]

✅ Deploy Preview for paragon-openedx ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	77fbd1e
🔍 Latest deploy log	https://app.netlify.com/sites/paragon-openedx/deploys/6758707ba224c400086540c6
😎 Deploy Preview	https://deploy-preview-3337--paragon-openedx.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[brian-smith-tcril]

if I understand the channel docs (https://semantic-release.gitbook.io/semantic-release/usage/workflow-configuration#channel) correctly this should make it so the release-23.x branch publishes to the @latest tag on npm

[brian-smith-tcril]

I'm not quite sure how prerelease and channel interact, but of all things to "test in prod" about this config it feels the least scary.

[brian-smith-tcril]

Based on https://semantic-release.gitbook.io/semantic-release/usage/workflow-configuration, this should make it so

• name: we're looking at the release-22.x branch
• range: this only publishes releases in the 22.x range of semantic versions
• channel: these releases are published to the 22.x tag on npm

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.82%. Comparing base (e96baef) to head (77fbd1e).
Report is 192 commits behind head on alpha.

Additional details and impacted files

@@           Coverage Diff           @@
##            alpha    #3337   +/-   ##
=======================================
  Coverage   93.82%   93.82%           
=======================================
  Files         229      229           
  Lines        3836     3836           
  Branches      916      916           
=======================================
  Hits         3599     3599           
  Misses        230      230           
  Partials        7        7           

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

[brian-smith-tcril]

closing in favor of #3341