Add workflow to publish OSS release to pub.dev

[hunterbreathat-wk]

Motivation

The OSS release process for over_React is manual currently, let's automate that.

Changes

• Add workflow to publish over_react to OSS pub.dev

Release Notes

• Add OSS publish workflow

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:

QA Checklist

• [ ] Tests were updated and provide good coverage of the changeset and other affected code
• [ ] Manual testing was performed if needed
  • [ ] Steps from PR author:
  • [ ] Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• [ ] A Frontend Frameworks Design member has reviewed these changes
• [ ] There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• [ ] For release PRs - Version metadata in Rosie comment is correct

[aviary2-wf]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.