release 1.3.0

[Borda]

What does this PR do?

version++ and other cleaning

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

[Borda]

this is just to have green badges or #7396 is fixed

[codecov]

Codecov Report

Merging #7404 (a9dc306) into master (d52e0a8) will decrease coverage by 0%.
The diff coverage is 50%.

@@          Coverage Diff           @@
##           master   #7404   +/-   ##
======================================
- Coverage      92%     92%   -0%     
======================================
  Files         200     200           
  Lines       12982   12983    +1     
======================================
- Hits        11911   11897   -14     
- Misses       1071    1086   +15     

[awaelchli]

I'll let you know about it
#7396

[carmocca]

🎉

[tchaton]

LGTM !

[kaushikb11]

💯

[leezu]

@Borda should #7362 be merged before the release?