[FLINK-36013] [runtime] Introduce the transition from Restarting to CreatingExecutionGraph state

[ztison]

What is the purpose of the change

The AdaptiveScheduler omits the WaitingForResources state when rescaling to avoid an additional waiting in that state.

Brief change log

• Pass the forcedRestart flag into the Restarting state
• Directs the state transition to the CreatingExecutingGraph instead of WaitingForResources if flag forcedRestart is set

Verifying this change

This change added tests and can be verified as follows:

• Added test to verify final state transition if the flag is set or not

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 applicable

[flinkbot]

CI report:

• fa688b9 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[XComp]

Follow-up PR after PR #25304 was closed "accidentally".

[XComp]

LGTM 👍