Extract proguard logic to new rules

[katre]

• Timestamp clearing now uses a small hermetic python script instead of relying on non-hermetic unzip and zip.
• Also split proguard and timestamp update actions for better caching.
• Moved fastutil proguard spec into third_party where it is used.

RELNOTES: None.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[katre]

The only test failure is an exec format error only on windows/arm64 (windows/x64 passes):

# Execution platform: //:default_host_platform
/usr/bin/bash: line 6: /c/b/4qcz3zc6/execroot/_main/external/rules_java++toolchains+remotejdk25_win_arm64/bin/jar: cannot execute binary file: Exec format error

This is pretty surprising: is there a misconfiguration with the windows/arm64 jdk?

[katre]

Hmm, adding a find call shows it really is an arm64 binary:

/usr/bin/bash: line 7: /c/b/k3n7yowv/execroot/_main/external/rules_java++toolchains+remotejdk25_win_arm64/bin/jar: cannot execute binary file: Exec format error
/c/b/k3n7yowv/execroot/_main/external/rules_java++toolchains+remotejdk25_win_arm64/bin/jar: PE32+ executable for MS Windows 6.02 (console), ARM64, 6 sections

@meteorcloudy , any ideas what's wrong here?

[katre]

I'm also tempted to rewrite this as a python script, which would probably also fix the windows issue. I'll think about it and get back to this later.

[katre]

Went ahead and used the script, and added actual rules, and re-arranged things somewhat. PTAL.