Update PR template and remove duplicates in release procedure

[i-oden]

Read this before submitting the PR

1. Always create a Draft PR first
2. Go through sections 1-5 below, fill them in and check all the boxes
3. Make sure that the branch is updated; if there's an "Update branch" button at the bottom of the PR, rebase or update branch.
4. When all boxes are checked, information is filled in, and the branch is updated: mark as Ready For Review and tag reviewers (top right)
5. Once there is a submitted review, implement the suggestions (if reasonable, otherwise discuss) and request an new review.

If there is a field which you are unsure about, enter the edit mode of this description or go to the PR template; There are invisible comments providing descriptions which may be of help.

1. Description / Summary

For some reason there's duplicated steps in the release procedure.

2. Jira task / GitHub issue

Is this a GitHub issue? --> Add the link to the github issue

Is this from a Jira task? --> If your branch does not contain info regarding the Jira task ID, put it here.

3. Type of change - Add label

What type of change(s) does the PR contain? For an explanation of the different options below, enter edit mode of this PR description template.

• type: breaking: Changes in this PR will cause existing functionality to not work as expected. The master branch of the API will no longer work with the CLI dev branch (and vice versa).
• type: feature: You've added new functionality or updated an existing one.
• type: bug: The PR fixes a bug.
• type: docs: The PR only updates documentation.
• type: dependency: You've updated a dependency version, e.g. a python package (in requirements.txt).
• skip-changelog: None of the above mentioned labels fit in. E.g. a new GitHub Action, a PR containing only tests, etc.

4. Additional information

• I have added an entry to the Sprintlog
• This is a PR to the master branch: If checked, read the release instructions
  • I have followed steps 1-8.

5. Actions / Scans

Make sure that the following checks/actions have passed.

• Black

• Prettier

• Pylint

• Yamllint

• Tests

• CodeQL

• Trivy

• Snyk

• TestPyPI

If an action does not pass and you need help with how to solve it, enter edit mode of this PR template or go to the PR template.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.65%. Comparing base (d687ba4) to head (d375606).

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #756   +/-   ##
=======================================
  Coverage   47.65%   47.65%           
=======================================
  Files          31       31           
  Lines        2925     2925           
=======================================
  Hits         1394     1394           
  Misses       1531     1531           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.