[FLINK-36424][yarn] Update deprecated YARN RM/NM callback handlers in YarnResourceManagerDriver

[ferenc-csaky]

What is the purpose of the change

(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)

Brief change log

• Create AMRMCallbackHandler that extends AMRMClientAsync.AbstractCallbackHandler, keeping the already existing logic from YarnContainerEventHandler.
• Create NMCallbackHandler that extends NMClientAsync.AbstractCallbackHandler, keeping the already existing logic from YarnContainerEventHandler.
• Adapt the related code to handle the new separate classes.

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

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

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

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

[flinkbot]

CI report:

• 2ea0c55 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[mateczagany]

I have looked into the YARN client code deeper, and this change should not affect the runtime behaviour. Moving away from deprecated interfaces/classes is always nice.

[ferenc-csaky]

Thanks @mateczagany, if no objections until then, I will merge this around Friday EOD (CEST).