chore: cicd - propagate changes to release pr from scripts

[jake-perkins]

Description

Fixes an issue related to a previous commit that caused changes to not be tracked/propagated to the newly minted release PR - 7d4577f

Related issues

Fixes:

Update create-release-pr script such that it creates a new commit with the expected changes housing the version changes

Manual testing steps

No Manual testing, will need to test from CI/CD invocation of manual workflow

Screenshots/Recordings

Before

N/A - CICD change

After

N/A - CICD change

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sethkfman]

LGTM