[MOO - 2286] : Release script fixes to automate Docs and Changelog PR in NT- 19-x-x

[saurabhchavan1711]

Description

In this PR

• Fixed the docs PR automation issues of polluted commits
• Moved the sync job from mendixMobile/docs fork to native-template repo
• Put publishing to docs and creating PR in native template changelog PR after release NT job , deleted the publishing changelog to docs job
• Added logic to raise PR in NT to update changelog after successful release

Checklist

To ensure this pull request meets the requirements for merging, please complete the checklist below:

• Release Note: As a part of the release process, an automated PR will be created for the Mendix Docs repository relevant to the changes introduced in this PR. Post release, please ensure that the release note accurately reflects the changes and impacts of this PR.
• Breaking Changes: This PR introduces breaking changes (e.g., changes that require updates to existing configurations, dependencies).
  • If yes, I have documented these breaking changes and provided guidance for users to adapt.
  • Details about breaking changes: [Provide details here, if applicable]

This PR contains

• Bug fix
• Feature
• Refactor
• Documentation
• Other (describe)

[MxKevinBeqo]

With error-handling in mind, I'm thinking what would happen in the scenario of updateNTReleaseNotes failing. From what it looks like now:

• A draft PR in native-template is created with no corresponding docs PR.
• On re-run, createPRUpdateChangelog() might throw ("A pull request already exists for..."), causing the entire script to fail on retry without ever reaching the docs step.

Maybe we can look into handling at least this error if it gets thrown whenever we call the pulls.create API. Ideally we can consider making the operation idempotent by editing the existing PR.