🚀 Feature

The current approach of setting manual consensus heights using getOrInitConsensusVersionTestHeights is difficult and error-prone, because a developer needs to know ahead of time how many consensus versions a particular snarkVM/snarkOS library/network has.

Alternative easier approaches could be:

• Option A: introduce a top-level build flag which will ensure the consensus_test_heights feature is enabled in the appropriate snarkVM Cargo.toml entries. Under the hood, this will automatically enable usage of the test consensus heights.
• Option B: introduce a function which reads ConsensusVersion::latest(), and then calls getOrInitConsensusVersionTestHeights with incrementing heights 0..ConsensusVersion::latest()+1.