[FLINK-40597][core] Fix input type validation for Types.UUID

[dylanhz]

What is the purpose of the change

Fix FLINK-40597: a DataStream created with explicit Types.UUID can fail input type validation for a non-lambda MapFunction<UUID, String> with Input mismatch: Basic type expected.

Brief change log

• Recognize java.util.UUID when validating explicitly specified basic type information.
• Leave UUID extraction without explicit type information unchanged (GenericTypeInfo<UUID> with Kryo by default). Automatic extraction as Types.UUID is tracked separately in FLINK-40546.

Verifying this change

• Added a fromData(Types.UUID, ...).map(...) regression test and a check that fromData(...) still infers GenericTypeInfo<UUID>.
• Confirmed the regression test fails without the fix and passes with it.
• DataStreamTest and TypeExtractorTest: 102 tests passed after rebasing onto master.
• Full ./mvnw clean verify was attempted. After resolving a local Python executable issue and resuming, verification stopped at flink-s3-fs-base: SeaweedFsTestContainerTest requires Docker, which is not installed locally. Subsequent modules have not been verified.

Does this pull request potentially affect one of the following parts:

• Dependencies: no
• Public API: yes, fixes validation in the existing @Public TypeExtractor; no API signatures change
• Serializers: no
• Runtime per-record code paths: no
• Deployment or recovery: no
• S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: Codex 0.147.0 (model: gpt-6)

[flinkbot]

CI report:

• ccfe431 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build