Include validmind-python and frontend in release notes

[sydneysugar]

Internal Notes for Reviewers

Responding to this story: https://app.shortcut.com/validmind/story/1781/roll-out-release-notes-process-to-other-repos

Updated release notes script to include validmind-python and frontend repos in the generated release notes.

Changes include:

• Moved release_highlights_template.qmd to templates folder
• No longer includes PRs if they have the 'internal' label
• Uses GitHub releases to get the list of PRs. E.g., this one in validmind-python
• Deals with duplicate PRs in the releases
• Adds '..' characters to the release_highlights_template.qmd file for the script to search and replace with actual content

External Release Notes

[nrichers]

@sydneysugar to complete roll-out for this functionality, we still need to:

• Add the CI checks to the validmind-python and frontend repos
• Add the PR template to the same repos.

I chatted with Andres a bit about the script, but we probably want to set up that meeting with him (or you can just meet with him 1:1) to make sure any concerns are addressed before we start rolling out to these repos.

Did you want to work on these items while I review your script?

[nrichers]

Wonderful updates to our release notes script, @sydneysugar! I left a few comments for you to address after testing, but this is looking really, really good. 🚀

[nrichers]

T-h-i-s close, @sydneysugar! After retesting, I have only a couple of minor formatting comments before this PR can be approved:

For bullet points, can we put the description on the same line, separated by a period, instead of breaking it out onto a new paragraph?

For example,

<!---Create troubleshooting page by @sydneysugar in [#116](https://github.com/validmind/documentation/pull/116) --->
- **Create troubleshooting page**

New troubleshooting guide for addressing technical issues with the Developer Framework.

should look like

<!---Create troubleshooting page by @sydneysugar in [#116](https://github.com/validmind/documentation/pull/116) --->
- **Create troubleshooting page**. New troubleshooting guide for addressing technical issues with the Developer Framework.

Without this change, the formatting looks off in the output, e.g.

Also, the heading repetition (one with a date) should be simplified. It would likely make sense to just remove the H2 so you're just left with one H1. It's nice to have the dat, though, as search might return a whole bunch of "Documentation updates" otherwise.

This is some great work from you all around. Looking forward to using this for our next release!

[nrichers]

@sydneysugar I accidentally pushed some local test changes to your PR, with an apology! I reset your branch to your last good commit and force pushed to remove my change, so your branch should now be in the same state as you left it. (Something something about muscle memory and me often committing and pushing in one go ...)

You might need to pull down your remote branch before pushing additional commits or simply force push your own changes with -f. That should resolve any errors due to git histories not matching.

[nrichers]

Fantastic work, @sydneysugar! This is a great script. Good to merge once the version is shown for the Platform UI. We should likely also do another process demo or go over the how-to for the folks contributing to the validmind-python and frontend repos.