Refactor FnHarness and FinalizeBundleHandler to use ScheduledExecutorService instead of ExecutorService.

[sjvanrossum]

FinalizeBundleHandler schedules tasks immediately onto the shared (Scheduled)ExecutorService. When the task runs it immediately blocks the thread until the earliest delay has expired. Doing so prevents the shared execution thread from being reused and may force the creation of new tasks which are truly able to execute immediately.

---

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.

[sjvanrossum]

Converting to draft, misread the implementation of FinalizeBundleHandler which only retains a single thread to perform its tasks. This change would have every finalize task co-schedule onto the execution thread pool. Depending on the perf impact of scheduling on the same pool, this PR can be amended to have FinalizeBundleHandler use a dedicated single threaded ScheduledExecutorService which should be equivalent to the current implementation that only differs in the amount of lines to maintain.