Cloudpickle configurable

[claudevdm]

Add the ability to override the default behavior of Cloudpickle by passing a CloudPickleConfig to cloudpickle.dumps.

The goal is to maintain default behavior, but add flexibility when different behavior is desired for example foregoing isinstance semantics for deterministic pickling of dynamic types.

This was copied from my cloudpickle fork https://github.com/claudevdm/cloudpickle/tree/cloudpickle-configurable, where I added unit test coverage for a bunch of different configurations and modified tests where appropriate.

I ran internal presubmit and tap for these changes and no issues found.

This is a prerequisite to relaxing dill pickler strict dependency #21298.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[claudevdm]

R: @tvalentyn

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers