chore(release-config): use a different place for the force-release tag

[RomainCoudour]

Instead of losing the scope of the commit with a CI-related instruction, move this instruction to the end of the commit, surrounded by squared brackets (like the skip ci GH Action instruction)

Example of usage : type(scope): subject [force release]

Sources:

• https://github.com/semantic-release/commit-analyzer#configuration
• https://github.com/semantic-release/commit-analyzer#release-rules
• https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular
• https://github.com/micromatch/micromatch#matching-features

[codeclimate[bot]]

Code Climate has analyzed commit b08cf3e3 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (70% is the threshold).

This pull request will bring the total coverage in the repository to 61.4%.

View more on Code Climate.

[forest-bot]

:tada: This PR is included in version 10.1.11 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release
• v10.1.11

Your semantic-release bot :package::rocket: