Allow to set timeout for finishing a remote bundle in Samza portable runner

[alnzng]

addresses #25030

We have observed that some UDFs(with bugs or imported some bad third-party libs) could hang the runner and SDK harness processes in Samza portable mode. Both runner and SDK harness processes are in a zombie state and have no data processing in this case, however, the processes are not able to be shut down although Samza runner provides some built-in timeout functionality.

This change will allow the users to set a timeout for closing a remote bundle in Samza portable runner. Once the timeout occurred, the runner and SDK processes will be shut down properly by Samza's built-in task timeout functionality if enabled.

---

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.

[alnzng]

@xinyuiscool please help take a look, thanks.

[mynameborat]

Can we add unit tests?

[alnzng]

Can we add unit tests?

I didn't do that because there is no test cases created for this SamzaDoFnRunners. But I can do it for this newly added method only.

[alnzng]

@mynameborat Thanks for helping review. I addressed your comments, let me know if you have other questions.

[xinyuiscool]

LGTM!