chore: update release templates

[andrablaj]

Description

Update release templates. Remove Product mentions. Remove mentions of teams and roles that don't exist anymore.

Code review checklist

• UI/UX backwards compatible: Test it works for the new design (enabled by default). And test it works in the old design, enable can_view_old_navigation permission to see the old design.
• Readable: Concise, well named, follows the style guide, documented if necessary.
• Documented: Configuration and user documentation on cht-docs
• Tested: Unit and/or e2e where appropriate
• Internationalised: All user facing text
• Backwards compatible: Works with existing data and configuration or includes a migration. Any breaking changes documented in the release notes.

Compose URLs

If Build CI hasn't passed, these may 404:

• Core
• CouchDB Single
• CouchDB Cluster

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

[mrjones-plip]

This is great Andrda! Thanks for continuing to iterate and make all our docs and processes consistent with the new team structure.

For sure approving - this is good to go - but do you think it's too soon to imagine what this will look like when it's not a medic person doing the release?

[andrablaj]

For sure approving - this is good to go - but do you think it's too soon to imagine what this will look like when it's not a medic person doing the release?

I was thinking about this today. I suggest we start imagining what that might look like in this separate issue. I don't think it's too soon, and we can do it in smaller steps.