[Bug]: Workflows occasionally fail due to network issues when fetching dependency metadata

[A1K28]

What happened?

Problem

Workflows that use the gradle step: :sdks:java:extensions:sql:generateFmppSources can occasionally fail due to network issues when trying to fetch matedata/snapshots.

Here is a recent example:

* What went wrong:
Execution failed for task ':sdks:java:extensions:sql:generateFmppSources'.
> Could not resolve all files for configuration ':sdks:java:extensions:sql:fmppTask'.
   > Could not resolve org.beanshell:bsh:[1.3,2.1).
     Required by:
         project :sdks:java:extensions:sql > com.googlecode.fmpp-maven-plugin:fmpp-maven-plugin:1.0 > net.sourceforge.fmpp:fmpp:0.9.14
      > Failed to list versions for org.beanshell:bsh.
         > Unable to load Maven meta-data from https://oss.sonatype.org/content/repositories/staging/org/beanshell/bsh/maven-metadata.xml.
            > Could not GET 'https://oss.sonatype.org/content/repositories/staging/org/beanshell/bsh/maven-metadata.xml'.
               > Read timed out

Retrieved from https://github.com/apache/beam/actions/runs/16674277126/job/47197213759

Potential Solutions

There are a few ways around this:

1. Use a retry mechanism
2. Embedded invocation with a jar
3. Run this task ':sdks:java:extensions:sql:fmppTask' only when it's needed (I havent identified this yet)
4. Cache the gradle build on successful workflows

Issue Priority

Priority: 3 (minor)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[A1K28]

fixed by #35764