Dtests marked with @ported_to_in_jvm can be skipped since 4.1

During the CASSANDRA-15536 epic we ported multiple Python dtests to in-JVM dtests.

The ported Python dtests are still present but marked with a new @ported_to_in_jvm annotation. JVM dtests didn't support vnodes at that time, so when a Python dtest is marked with that annotation it's only run for vnodes config, whereas it's skipped if vnodes are off.

However, we have had support for vnodes on JVM dtests since 4.1. Thus, I think we should modify the @ported_to_in_jvm annotation to also skip configs with vnodes if all the nodes are in 4.1 or later.