Release v0.24.3

[lidel]

• pass CI in Kubo chore: boxo v0.24.3 and p2p-forge v0.0.2 kubo#10572
• bump changelog and version.json
• add release label

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 60.37%. Comparing base (977edea) to head (f397e79).
Report is 4 commits behind head on release.

Files with missing lines	Patch %	Lines
...ernal/providerquerymanager/providerquerymanager.go	0.00%	1 Missing ⚠️

@@             Coverage Diff             @@
##           release     #713      +/-   ##
===========================================
- Coverage    60.49%   60.37%   -0.12%     
===========================================
  Files          243      243              
  Lines        31025    31025              
===========================================
- Hits         18768    18731      -37     
- Misses       10598    10628      +30     
- Partials      1659     1666       +7     

Files with missing lines	Coverage Δ
...ernal/providerquerymanager/providerquerymanager.go	88.21% <0.00%> (ø)

... and 11 files with indirect coverage changes

[github-actions]

Suggested version: 0.24.3

Comparing to: v0.24.2 (diff)

Changes in configuration file(s):

(empty)

gorelease says:

gorelease: go: loading module retractions for honnef.co/go/tools@v0.0.1-2019.2.3: module honnef.co/go/tools@v0.5.1 requires go >= 1.22.1 (running go 1.22.0)

gocompat says:

HEAD is now at 814ad5dc Merge pull request #707 from ipfs/release-v0.24.2
Previous HEAD position was 814ad5dc Merge pull request #707 from ipfs/release-v0.24.2
Switched to branch 'release'
Your branch is up to date with 'origin/release'.

Cutting a Release (and modifying non-markdown files)

This PR is modifying both version.json and non-markdown files.
The Release Checker is not able to analyse files that are not checked in to release. This might cause the above analysis to be inaccurate.
Please consider performing all the code changes in a separate PR before cutting the release.

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.