[FLINK-39641][runtime-web] Fix unstable position of the Rescales Tab

[RocMarshal]

What is the purpose of the change

[FLINK-39641][runtime-web] Fix unstable position of the Rescales Tab

Brief change log

• Fix the target position of Rescales finding logic

Verifying this change

• Before the fix:

• After the fix:

I followed the reproduction steps[1] and tried 10 times, the issue no longer occurred.
[1] https://issues.apache.org/jira/browse/FLINK-39494

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)

---

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

• Yes (please specify the tool below)

[flinkbot]

CI report:

• 5b985f8 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[spuru9]

@RocMarshal Can you add the before and after image to the PR?

[RocMarshal]

Thanks @spuru9 for your reminder.
I added the images.

PTAL.

[spuru9]

Thanks @spuru9 for your reminder. I added the images.

PTAL.

I saw a similar fix in #28044, Is this something different?

[RocMarshal]

HI， @spuru9 It seems that the fix you mentioned does not fully resolve the current issue, which is part of the reason why this PR is needed.

[och5351]

Hi, @spuru9 !

These are actually two different issues. The previous one: when the adaptive scheduler was enabled, after viewing a batch job screen (where the Rescales tab didn't exist) and then navigating to a streaming job overview, the tab order would shift unexpectedly.

The current one: when a cluster without the adaptive scheduler is restarted with it enabled, viewing the job in the same browser tab shows incorrect tab order—but refreshing the page or opening a new tab displays it correctly.

Ref: https://issues.apache.org/jira/browse/FLINK-39494

It's a minor issue, but RocMarshal raised it to maintain UI consistency.

cc. @RocMarshal

[RocMarshal]

Thanks @och5351 for the clarify.

[spuru9]

LGTM

[RocMarshal]

Thanks all revolved in the PR, Merging...