Prepare Jdeps extension for K2 implementation

[jbarr21]

This PR makes 3 small changes to the JDeps extension in preparation of adding the K2 impl (#843):

1. Ensure that we set the correct argument to enable K2 in KotlinJvmTestBuilder.java. We also avoid resetting the option by modifying the existing infoBuilder instead of using CompilationTaskInfo.newBuilder().
2. Since the K1 & K2 flows will be different, they will track classes in a different order. We need to sort the deps in the proto so that we can properly assert their equality.
3. We split out the Jdeps creation logic from JdepsGenExtension into a new base class that can be extended by the K2 implementation. There are no logic changes in this refactor.

[Bencodes]

Can you take a look at the KtLint errors?

[jbarr21]

Can you take a look at the KtLint errors?

@Bencodes already fixed. the test failure passes locally though. any thoughts?

❯ bazel test //src/test/kotlin/io/bazel/worker:WorkerEnvironmentTest
...
INFO: Found 1 test target...
Target //src/test/kotlin/io/bazel/worker:WorkerEnvironmentTest up-to-date:
  bazel-bin/src/test/kotlin/io/bazel/worker/WorkerEnvironmentTest.jar
  bazel-bin/src/test/kotlin/io/bazel/worker/WorkerEnvironmentTest.jdeps
INFO: Elapsed time: 24.900s, Critical Path: 16.03s
INFO: 365 processes: 17 internal, 312 darwin-sandbox, 36 worker.
INFO: Build completed successfully, 365 total actions
//src/test/kotlin/io/bazel/worker:WorkerEnvironmentTest                  PASSED in 0.4s

[Bencodes]

Ah this one is flaky. Should be good to merge.

[Bencodes]

Any reason this needs to be a base class and not just some independent class that both implementations can call into?

[jbarr21]

either one works, but I figured I was going to use a common base for the 2 extensions anyways