Stop checking maxMajorPV in the header envelopeCheck

[nfrisby]

(This tech debt issue is only on the now unused Jira, so I'm creating this Issue instead.)

See IntersectMBO/ouroboros-network#3891 (comment) for more context.

[nfrisby]

@amesgen and I considered some possibilities.

• It seems premature to reject a block/transaction that contains a ledger proposal that uses a protocol version beyond the maximum.

• My initial intuition was that ticking across the epoch boundary (which is when the actual protocol version would increase beyond our local limit) should fail in this case. But at the moment, ticking cannot fail. If it could fail here, then in this particular case I think node should simply shutdown, with a message that the software needs to be updated.

• Maybe the ChainSel logic---which is where the most fundamental tick happens---could check for this and raise a proper exception there.