What is the purpose of the change

For some config options like taskmanager.runtime.sort-spilling-threshold ,taskmanager.runtime.max-fan ... etc. used for sorting and spilling, we get this option value from JobConfiguration. In fact, these parameters should be only available in the TaskManagerConfiguration now. The current change is to think of them as cluster-level configurations. The reason is that from the key of these Option, they are all prefixed with taskmanager.
I'm not sure whether consider this as job-wise conf is better.

Brief change log

• Using TaskManagerConfiguration to load these config options.

Verifying this change

Manual testing.

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