Monotonic implements msgp.Marshaler and msgp.Unmarshaler, writing its
reference point as a msgpack array of Unix seconds and nanoseconds.
Decode reads that form as well as the go-codec timestamp. Encode keeps
writing the go-codec timestamp until encodeWithMsgp is set, so a node
rolled back to an older release can still restore its crash state.

Encode still writes go-codec's msgpack timestamp so a node rolled back
to an older release can restore its crash state. Decode also accepts
msgpack nil and an int64 of Unix nanoseconds, so a later release can
switch Encode to that form without reflection.

Use generated msgp for AccountTotals in the catchpoint label, whose
msgp encoding is tested to match go-codec. Exclude the offline
tools/debug programs from the reflection rule, and mark goal inspect
and the monotonic clock's time.Time encoding.

Convert the algoh block fetch to generated msgp, since
rpcs.EncodedBlockCert has it. The remaining uses decode types with no
generated msgp code, or read actions persisted by older releases.

golangci-lint v2 ignores the forbidigo analyze_types and p keys, so
the rule never ran. Rename them to analyze-types and pattern, scope the
crypto/network exclusion to this rule's message so later forbidigo
rules can apply repo-wide, and convert the existing require.Error and
assert.Error calls in crypto/ and network/ tests.

These have been encoded with msgp since #4644, so no running release
writes them with go-codec. Actions keep their reflection fallback
because released binaries still encode them with go-codec.

# Conflicts:
#	agreement/persistence.go
#	rpcs/blockService.go
#	rpcs/blockService_test.go
#	rpcs/msgp_gen.go
#	rpcs/msgp_gen_test.go

fix: resolve ci findings; skip migration for deprecated