Support ranges for dynamic types' lengths

Related: https://github.com/runtimeverification/kontrol/issues/353

Dynamic array support implemented in https://github.com/runtimeverification/kontrol/pull/321 relies on the assumption that the array and its elements' length is fixed to a particular concrete value, e.g.,

    /// @custom:length _withdrawalProof: 10,
    /// @custom:length _withdrawalProof[]: 600,
    function test_finalizeWithdrawalTransaction_paused(
        bytes[] calldata _withdrawalProof
    )

The feedback we received from the Optimism team, however, suggests that it'd be better if allowed specification of a range (min/max bounds) instead of a fixed value for bytes (and array) length. For example, in this test, the min proof length is 5 and the max is 8. The element lengths range from 32 to 532 bytes, so using 32 and 600 as the bounds would be better.

Start by reading related issue #353 and dynamic array support in pull request #321, then trace how the custom:length annotations in the Solidity example are parsed and applied. Define how minimum and maximum bounds should be represented for arrays and elements, and verify that the example accepts proof lengths of 5–8 and element lengths bounded by 32–600.