[FLINK-17295][runtime] Refactor the ExecutionAttemptID to consist of ExecutionGraphID, ExecutionVertexID and attemptNumber

[zhuzhurk]

What is the purpose of the change

A meaningful ExecutionAttemptID can help in many places, including improve log readability and add an easy way to find the corresponding execution vertex.

Brief change log

• Refactor the ExecutionAttemptID to consist of ExecutionGraphID, ExecutionVertexID and attemptNumber(int type)
• Refactor the usages of ExecutionAttemptID to ensure param consistency

Verifying this change

This change is already covered by existing tests.
Manual e2e tests are run against this change.

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

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

Documentation

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

[flinkbot]

CI report:

• 0b0e95f Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[zentol]

I also left a comment in JIRA, PTAL.

[zhuzhurk]

Thanks for reviewing! @zentol @KarmaGYZ
Merging.