<!--
ICON

---------------------------------------------------------------
Copyright (C) 2004-2024, DWD, MPI-M, DKRZ, KIT, ETH, MeteoSwiss
Contact information: icon-model.org

See AUTHORS.TXT for a list of authors
See LICENSES/ for license information
SPDX-License-Identifier: CC0-1.0
---------------------------------------------------------------
-->

## What is the new feature
Add changelog automation
## How is it implemented
Now we have our first release, I propose that we start keeping track of the changelogs.  
This MR sets the changelog templates that would be automatically added when a release tag is created.  
We would have to edit the squashed commit message and choose a changelog category for the release-bot to grab the message.  
[Here](https://about.gitlab.com/blog/2023/11/01/tutorial-automated-release-and-release-notes-with-gitlab/) and [here](https://docs.gitlab.com/ee/user/project/changelogs.html

) are references for the method.

## Mandatory steps before review
- [x] Gitlab CI passes _(Hint: use `make format` for linting)_ 
- [x] New feature is covered by additional unit tests
- [x] Mark the merge request as ready by removing `Draft:`

## Mandatory steps before merge
- [x] Reviewed by a maintainer
- [x] Incorporate review suggestions
- [x] Remember to edit the commit message and select the proper changelog category (feature/bugfix/other)

**You are not supposed to merge this request by yourself, the maintainers of fortan-support take care of this action!**

Approved-by: Jonas Jucker <jonas.jucker@env.ethz.ch>
Merged-by: Yen-Chen Chen <yen-chen.chen@kit.edu>
Changelog: other

Signed-off-by: Terry Cojean <terry.cojean@kit.edu>

- /.gitlab/merge_request_templates/new_feature.md
- /.gitlab/merge_request_templates/feature.md
- /.gitlab/merge_request_templates/bugfix.md
- /README.md