version bumps for `v0.3.6`

[plebhash]

in relation to release/v0.3.5:

• integration_tests_sv2: v0.1.1 -> v0.1.2
• bitcoin_core_sv2: v0.1.2 -> v0.1.3
• stratum-apps: v0.3.2 -> v0.3.3
• pool_sv2: v0.2.2 -> v0.2.3
• jd_server_sv2: v0.1.2 -> v0.1.3
• jd_client_sv2: v0.1.5 -> v0.1.6
• translator_sv2: v0.2.4 -> v0.2.6

note about version gap on translator_sv2:

• was published as v0.2.4 during sv2-apps v0.3.5 version bumps for v0.3.5 #474 (comment)
• was published as v0.2.5 during sv2-apps v0.4.0 version bumps for v0.4.0 #359 (comment)
• will be published as v0.3.0 during sv2-apps v0.5.0 version bumps for v0.5.0 #487 (comment)

when we push the v0.3.6 tag on sv2-apps, CI will try to publish translator_sv2, for which we'll have to use v0.2.6

(hopefully) this will not cause any issues

---

perhaps we should consider something like this for sv2-apps: stratum-mining/stratum#2158

[plebhash]

v0.3.6 is no longer planned, see #504 (comment)