chore: activate branch ruleset

[bniladridas]

Sync the repository-managed ruleset JSON with the now-active GitHub ruleset.

• rename the local ruleset file to main-branch-protection.active.json
• set enforcement to active

This change had to merge through a PR because the main branch ruleset was already enforced.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 470f25e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

✅ Pre-commit check ran - no fixes needed.

[bniladridas]

• already on main
  • 07617ed — chore: repo-managed release automation
  • 76f0665 — chore: align ruleset enforcement
• pending in this PR
  • 470f25e — chore: activate branch ruleset

Direct push of 470f25e to main was rejected by the newly active ruleset, so this PR is the required final sync to keep the repo-managed ruleset file aligned with the live GitHub ruleset.