[TEST] Extend unicast ports generation to support more concurrent clusters

The current `UnicastZen` only supports up to 10 different clusters per jvm, after which it generates ports that overlap between different jvms.

Make it possible to run multiple tests with unicast configuration, by assigning ports based on their test scope.
Every jvm still gets its own port range based on the jvm id, but we now make sure that the different jvms ranges never overlap. The global cluster gets a reserved port range, while SUITE and TEST scopes are treated equally, just assuming that they never run concurrently on the same jvm, thus ports can be safely reused.
> why not round robin on this? I think the randomness still allows us to have collisions and will keep us wondering.

the assumption is that only one cluster with either `SUITE` or `TEST` is on at a given time within a jvm, so there shouldn't be conflicts. Randomizing is not strictly necessary (we just have to skip 0 and make sure not to go above 9) but it does help verifying our assumption? I am conflicted here...

> +1 on the insight that suite and test scope don't co-exists! Also, this makes us one step closer to using it randomly in our global cluster scope.

Indeed, this change should make this possible as the next step!