fix: TRAC-514 - accept ticket-first commit format in release flow and use PAT for release PRs

[parthshahp]

Summary

Fixes two release-flow problems in one change (LTRAC-529 / TRAC-514):

1. Ticket-first PR titles broke the release pipeline

Commits using the new BigCommerce format (TICKET-123: type(scope) - subject, as enforced by @bigcommerce/validate-commits) failed in two places:

• the commitlint gate in the release workflow
• @semantic-release/commit-analyzer

Fix: new commit-format.cjs exports shared parserOpts accepting both the new ticket-first format and the legacy conventional format. It's wired into commitlint.config.cjs and a new release.config.cjs (replacing .releaserc, which as JSON couldn't share the regex). type-enum is now the union of config-conventional and validate-commits types.

2. LTRAC-529: bot release PRs never ran CI automatically

Release PRs opened by semantic-release-github-pullrequest-fixed with GITHUB_TOKEN don't trigger PR workflows (9.0.2 and 9.0.3 both needed manual re-runs). The plugin prefers env.GH_TOKEN_RELEASE when creating the PR, so release.yml now passes the PAT there — release PRs will be authored by the PAT user and trigger checks automatically.

Testing

• commitlint passes both formats (verified against 7 real commit subjects from history) and still rejects malformed messages
• commit-analyzer with the new parserOpts: TRAC-1206: feat - … → minor, feat! → major, fix → patch, chore/docs → no release
• semantic-release cosmiconfig resolves release.config.cjs; eslint passes

[parthshahp]

This whole thing isn't strictly necessary but just a nice to have to be consistent across BC repos. Let me know if we want to keep this scoped to just the GH_TOKEN issue.

[github-actions]

🎉 This PR is included in version 9.1.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 9.1.0

Your semantic-release bot 📦🚀