support JVM compiler option sets as in Pants v1

[tdyas]

User request: Support JVM compiler option sets (or equivalent) as was supported in Pants v1. The user's specific use case is varying the options used for compiling test Scala files from the options used when compiling regular Scala files.

[tdyas]

Some v1.30.x code: https://github.com/pantsbuild/pants/blob/1.30.x/src/python/pants/option/compiler_option_sets_mixin.py

[stuhood]

Although it's possible that the entire UX could be lifted from v1, the big difference to consider is how this should interplay with __defaults__.

[tdyas]

1. Are there any good docs on the v1 semantics? Specifically, I see that v1 has the notion of "enabled" and "disabled" compiler option sets.
2. Naming bike shed: Should option sets like this be particular to "compilers" or to "tools" in general? I.e., just name it jvm_option_set and those options could be used by a target for purposes other than compilation (for example, running code).
3. Should references to option sets be via the address of the option_set target instead of an option set name? This would keep addresses as the main way to name targets including option set targets.