Fix v0.4.0 releasenotes + templates

[yardasol]

Summary of changes

This PR adds content from #98 and #115 to the v0.4.0 release notes.

This PR also adjusts the formatting for the release notes so they display better on GitHub, and adds a line to the template.rst file to indicate that the newest release notes on the master branch in the online docs are in production.

This PR adds a line to the next-minor-release workflow to remove the 'in-production' note when the current draft release is published.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Required for Merging

• I have read the CONTRIBUTING document.
• My code follows the code style of this project.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• My change is a source code change
  • I have added/modified tests to cover my changes
  • I have explained why my change does not require new/modified tests
• All new and existing tests passed.
  • CI tests pass
  • Local tests pass (including Serpent2 integration tests)
• I have recorded my changes in the changelog for the upcoming release

Associated Issues and PRs

• Issue: closes [Bug]: Update 0.4.0 release notes #121

Associated Developers

• Dev: @munkm

Checklist for Reviewers

Reviewers should use this link to get to the
Review Checklist before they begin their review.

[abachma2]

This looks good to me. If no one else has comments by the end of the day I'll merge it.

[yardasol]

@abachma2 the bug with miniforge that was causing our actions to fail has been fixed (see #1480 in mamba, #262 in miniforge). So the actions that will run when this is merged should all pass now

[yardasol]

Scratch that. While the bug has been fixed and the mamba version updated in miniforge, I'm still running into the same bug on the workflow. My guess is that the release hasn't been fully published yet (it's just a prerelease), so the version of miniforge that has the fix isn't getting picked up by the setup-miniconda action.

[yardasol]

@abachma2 actions are working again. Can you go ahead and merge?