Fix handling of FCnt resets and 32-bit FCnt rollovers

[rvolosatovs]

Summary

Closes #3728
Refs #3743

Changes

• Fix msgpack encoding of sessions
• Fix FCnt check on reset for devices with 32-bit frame counters
• Migrate sessions created on 3.11 snapshot to new format

Testing

Unit tests, integration testing

ses=$(cli dev get test-app2 test-dev-c --session)
dev_addr=$(echo "${ses}" | jq -r '.session.dev_addr')
f_nwk_s_int_key=$(echo "${ses}" | jq -r '.session.keys.f_nwk_s_int_key.key')
echo "${ses}" | jq
cli simulate gateway-uplink --lorawan-phy-version "1.0.3-a" --lorawan-version "1.0.3" --gateway-id test-gtw --dev-addr "${dev_addr}" --f_nwk_s_int_key "${f_nwk_s_int_key}" --f_cnt 0x42
cli simulate gateway-uplink --lorawan-phy-version "1.0.3-a" --lorawan-version "1.0.3" --gateway-id test-gtw --dev-addr "${dev_addr}" --f_nwk_s_int_key "${f_nwk_s_int_key}" --f_cnt "${1:-"0x02"}"

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.

[KrishnaIyer]

@rvolosatovs: This only affects v3.11 and doesn't need a backport right?

[rvolosatovs]

yes

[htdvisser]

Not sure why GitHub decided to request code-owner review on a draft PR. Only quickly glanced over it.

[htdvisser]

Looks okay to me. We're definitely going to need to verify that this all works in a new rc, so let's get that going as soon as this is merged.