version bumps for v1.3.0

[plebhash]

unfortunately cargo semver-checks will only warn us about MAJOR bumps, but MINOR and PATCH bumps still require our own discipline

in the past we had some discussions about bumping MINOR and PATCH crate versions on the same PR that introduces the changes, or right before doing the release

there's pros and cons with both strategies

if we bump on the same PR that introduces the changes:

• pro: we don't forget to bump the crate
• con: we could potentially bump 2x before publishing, and end up with version gaps on crates.io (e.g.: 1.2.0 then 1.4.0)

if we bump right before the release:

• pro: we don't risk bumping 2x before publishing
• con: we risk forgetting to bump, in case the change happened a long time ago

a good compromise is to keep a dedicated issue to keep track of changes for every release

every time we introduce some change, we take note here

and then before we do the release, we use this issue to analyze all the needed version bumps before publishing the crates

---

we should use this issue to keep track of the needed version bumps before v1.3.0

[plebhash]

starting with #1238

we need to bump MINOR for noise_sv2