Adds an unsafe delete option to be used for garbage collection of multi_process_shared objects. This allows cleanup of multiprocess objects even if some references have been entirely lost (e.g. due to running in a subprocess mode) or if its unclear when they'll be invoked again (because Beam may not schedule work to that DoFn for a bit).

This is intentionally unsafe and should only be used when other synchronization mechanisms are in place to prevent usage of the already deleted object. For example, this will be used as part of our runinference timeout feature - for more details see https://docs.google.com/document/d/19ves6iv-m_6DFmePJZqYpLm-bCooPu6wQ-Ti6kAl2Jo/edit#heading=h.cfdh3ijyabi3

Part of #32137

---

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.