[FLINK-37441] Rename factoryHierarchy to typeHierarchy for TypeExtractor

[beliefer]

What is the purpose of the change

This PR proposes to rename factoryHierarchy to typeHierarchy due to it is just a List<Type> and doesn't related to factory.

Brief change log

Rename factoryHierarchy to typeHierarchy for TypeExtractor

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

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:

• 2b8d331 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[davidradl]

nit: it is not a hierarchy it is a list - if we are changing this why not change to something more representative like candidateTypeList and rename the related variables to be Lists not hierarchy.

[beliefer]

The typeHierarchy also is a list, so I followed the style.
But I think you said is right, let's use typeHierarchyList and newTypeHierarchyList.

[beliefer]

After a second thought. I guess the original author use the name typeHierarchy due to the list contains the type information according to the hierarchy.
Such as:
{class java.lang.String, class java.lang.Object}.
So let me temporarily use the name typeHierarchy. I am willing to use typeHierarchyList and newTypeHierarchyList if more reviewer suggest it.

[beliefer]

@flinkbot run azure

[beliefer]

cc @1996fanrui