[Task]: Deprecate Twister2 runner

### What needs to happen?

context: https://lists.apache.org/thread/2v5m0y8m27lx6w2pn80jxd38qy7c1fdx

The twister2 repo [1] hasnt seen a change in 5 years and the twister2 runner directory has had a similarly low level of activity.

As part of Beam 3.0 effort of modernizing runners, unmaintained non-portable runners are subject to deprecation (#35836).

[1] https://github.com/cylondata/twister2

### Issue Priority

Priority: 2 (default / most normal work should be filed as P2)

### 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

Start with the Twister2 runner directory and the linked deprecation context, including issue #35836; the issue does not name specific files or tests. Determine Beam’s deprecation process and identify the runner references that require handling; done means the Twister2 runner is deprecated consistently with the Beam 3.0 modernization effort.

Written by the indexing model from the issue text.