Enrich the TestEnableDevelopmentNetworkProtocols UX

As part of adding a new `NodeToNodeVersion`, we experienced an unfortunate downside of the currently limited expressivity of `TestEnableDevelopmentNetworkProtocols`: both Consensus and Networking teams have new features we’d like to gate. The flag is currently boolean, so the user either had to enable both new features or none. In this case, it would make sense to let the user choose between just the Consensus feature or both features.

This task is to make at least that additional level of granularity possible, on the Consensus side (separate work would be needed in cardano-node repo).

# Acceptance criteria
The Consensus side of this interface (currently `srnEnableInDevelopmentVersions`) enables the client interface to choose between multiple development versions (at the very least, the possible options would be cumulative).

(There needs to be a separate ticket to track the `cardano-node` side implementation of the same idea.)