[FLINK-27902][runtime] Refactor ResultPartitionType to decouple scheduling and partition release logic

[reswqa]

What is the purpose of the change

Refactor ResultPartitionType to decouple scheduling and partition release logic

Brief change log

• *Introduce ConsumeType indicates when can the downstream consume the upstream. *
• Introduce ReleaseType indicates who is responsible for releasing the result partition.
• Using ConsumeType and ReleaseType instead of isPipelined and isReconnectable in scheduling and partition release related code.
• Remove useless isPipelined, isBlocking and isReconnectable in ResultPartitionType.

Verifying this change

This change is already covered by existing tests

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:

• 365f923 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[xintongsong]

Thanks for opening the PR, @reswqa. The refactor looks good in general. I have only a few comments. Please take a look.

[xintongsong]

LGTM. There are only one minor comment, plus that commit messages should indicate the relevant component. I'll fix them while merging this.