build(deps-dev): bump semantic-release from 19.0.5 to 21.0.6

[dependabot]

Bumps semantic-release from 19.0.5 to 21.0.6.

Release notes

Sourced from semantic-release's releases.

v21.0.6

21.0.6 (2023-06-28)

Bug Fixes

• get correct version if prerelease branch shares version with ... (#2416) (e4229f9)

v21.0.5

21.0.5 (2023-06-09)

Bug Fixes

• deps: update dependency marked to v5 (452e1fa)

v21.0.4

21.0.4 (2023-06-09)

Bug Fixes

• deps: update dependency @​semantic-release/error to v4 (d259350)

v21.0.3

21.0.3 (2023-06-02)

Bug Fixes

• bump @semantic-release/commit-analyzer to v10.0.0-beta.1 (4a6b31f)
• bump @semantic-release/github to 9.0.0-beta.2 (#2818) (6f19d77)
• deps: updated the beta plugins to stable versions (3941018)

v21.0.3-beta.3

21.0.3-beta.3 (2023-06-02)

Bug Fixes

• deps: updated the beta plugins to stable versions (3941018)

v21.0.3-beta.2

21.0.3-beta.2 (2023-05-30)

Bug Fixes

• bump @semantic-release/commit-analyzer to v10.0.0-beta.1 (4a6b31f)

... (truncated)

Commits

• e4229f9 fix: get correct version if prerelease branch shares version with ... (#2416)
• 9514e20 ci(action): update ossf/scorecard-action action to v2.2.0 (#2854)
• 5fcdc27 ci(action): update github/codeql-action action to v2.20.1 (#2853)
• 1260d3a ci(action): pin dependencies (#2850)
• 9ebabe1 ci(ossf-scorecard): added workflow calculating scorecard metrics (#2848)
• e39ae90 test(integration): properly waited for the image pulls to complete (#2842)
• 39d2a05 chore(deps): update dependency sinon to v15.2.0 (#2844)
• 45eb11a chore(deps): update dependency c8 to v8 (#2833)
• 71e805d chore(deps): update dependency ava to v5.3.1 (#2839)
• 9f660ff chore(deps): lock file maintenance (#2841)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[dependabot]

Superseded by #345.