[Task]: Deprecate Jet runner

[Abacn]

What needs to happen?

Beam Hazelcast Jet runner is based on Hazelcast Jet 4.0, which is eol. The old website for Hazelcast Jet (jet.hazelcast.org) is expired (see #35565). Hazelcast Jet merged to Hazelcast as of version 5.0 ([1], and new Hazelcast website hazelcast.com).

As part of Beam 3.0 effort of modernizing runners, unmaintained non-portable runners are subject to deprecation (#35836). We should upgrade Jet runner to Hazelcast 5 API and/or move to portable runner API, or have to mark it as deprecated as of Beam 3.0.

Note that from [1] current Beam Jet runner pipeline should still be able to run on Hazelcast 5.

[1] https://docs.hazelcast.com/hazelcast/5.5/migrate/upgrading-from-jet

Issue Priority

Priority: 3 (nice-to-have improvement)

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

[Abacn]

No actions since this issue is raised. Go through the path of deprecating Jet runner and move to milestone 3