[FLINK-37581] Avoid duplicate calculation for total Flink memory

[beliefer]

What is the purpose of the change

This PR aims to avoid duplicate calculation for total Flink memory.
Currently, there are duplicate calling on calculateTotalFlinkMemoryFromComponents while creating TaskExecutorMemoryConfiguration.
The first caller is the method create of TaskExecutorMemoryConfiguration.
The second caller is the method calculateTotalProcessMemoryFromComponents of TaskExecutorResourceUtils.

Brief change log

Avoid duplicate calculation for total Flink memory.

Verifying this change

This change is already covered by existing tests, such as (TaskExecutorResourceUtilsTest).

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)

[flinkbot]

CI report:

• 20fae0e Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[beliefer]

ping @XComp @tillrohrmann @KarmaGYZ cc @1996fanrui @davidradl @GOODBOY008

[plazma-prizma]

Thanks for the PR @beliefer . I think this is a tiny improvement on the number of addition operations. Arguably, it might be useful but doesn't seem crucial to me.

Approving it but I think it is okay to not merge this change as well.

[SuryaSrikar]

By any chance do you know the time reduced by avoiding these duplicate calls?

[beliefer]

I think this change has a little improvement that cannot be watched from end to end easily.