Release (submission) date automation

### What is this about?

This ticket will leverage release data automation:

- Update Notion
- Update GH Project Boards (https://github.com/orgs/MetaMask/projects/86/views/3)

The automation shall fetch release dates from Runway (cut date, validated date, rollout started date, rollout completed date) and update Notion + GH Project Board with dates, such that Runway becomes the unique source of truth.

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [x] Engineering (needed in most cases)
- [ ] Design
- [x] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [x] Other (please specify)

### References

_No response_

Start by reviewing the release-data automation context and the linked GitHub Project Board, then clarify how Runway, Notion, and GitHub should exchange the four release dates. Done means Runway is the unique source of truth and the specified dates are updated in both destinations, with acceptance criteria and validation steps defined.

Written by the indexing model from the issue text.