Strip unnecessary Bazel server jar contents

[fmeum]

fastutil is very large and thus stripped (but not obfuscated) with proguard. The Auto* processors do not need to be included into the release binary, only their annotations.

Also removes some third_party targets that are unused.

Bazel binary size on macOS is 65 MB before and 53 MB after this change.

Work towards #22722

[fmeum]

@meteorcloudy This PR touches third_party in a non-trivial way: It adds Maven dependencies that //third_party will depend on and also has to adjust a test that depends on //third_party. I don't know how I need to split this up.

[meteorcloudy]

No worries, the third_party files touched in this PR are all imported, so we can just go through the normal import process.

[meteorcloudy]

The complete list of imported files are:

    return glob(
        include = ["**"],
        # Keep existing sources from git.
        exclude = [
            "CHANGELOG.md",
            "COPYRIGHT",
            "LICENSE.txt",
            "third_party/android_dex/**",
            "third_party/asm/**",
            "third_party/googleapis/**",
            "third_party/def_parser/**",
            "third_party/grpc-java/**",
            "third_party/grpc/**",
            "third_party/jarjar/**",
            "third_party/java/**",
            "third_party/pprof/**",
            "third_party/py/**",
            "third_party/remoteapis/**",
            "third_party/turbine/**",
            "third_party/zlib/**",
        ],
    ) + glob(include = ["third_party/**/MODULE.bazel"])

[fmeum]

@meisterT This required some after the fact fixes to the JAR to make it deterministic.

[meteorcloudy]

@fmeum Unfortunately, our internal policy doesn't allow importing this file under bazel's own third_party to prevent potential bundling dependencies. I assume this is authored by you, right? Can you move this to the tools directory instead?

[fmeum]

Do you mean that I should move the file into tools, but keep the genrule referencing it in third_party? Wouldn't that cause the file to show up under @bazel_tools//tools?

[meteorcloudy]

Yes, as long as it's not included in

bazel/tools/BUILD

Line 43 in dd48c1a

name = "embedded_tools_srcs",

, it should be fine.

[meteorcloudy]

So maybe under tools/proguard?

[fmeum]

I moved it into tools and added it to exclude so that excluding it is documented as an explicit choice.

[meteorcloudy]

SG, thank you!

[meteorcloudy]

To fix the CI breakage, you probably have to sync to HEAD.