Revert three commits related to supporting custom coder in reshuffle

[shunping]

• Fix custom coder not being used in Reshuffle (global window) (Fix custom coder not being used in Reshuffle (global window) #33339)
• Fix custom coders not being used in Reshuffle (non global window) Fix custom coders not being used in Reshuffle (non global window) #33363
• Add missing to_type_hint to WindowedValueCoder Add missing to_type_hint to WindowedValueCoder #33403

It is causing some internal test failure so we revert it for now.

[chamikaramj]

LGTM. Thanks.

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[shunping]

Failed tests are unrelated to the changes.

[robertwb]

Just a thought, as this changes coders in some cases, should this be guarded by the update compatibility flag? https://github.com/apache/beam/blob/master/sdks/python/apache_beam/options/pipeline_options.py#L592

[shunping]

As the flag is defined in "StreamingOptions", is it previously designed for using in streaming case?

[kennknowles]

As the flag is defined in "StreamingOptions", is it previously designed for using in streaming case?

Yes, it is designed for "streaming update" where you may have an in-progress aggregation in a shuffle when you do a pipeline update. Then you need the state to be compatible.