[BEAM-13981] Remove Spark Runner specific code for event logging

[iemejia]

R: @aromanenko-dev
CC: @ibzib

Please add a meaningful description for your change here

---

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

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• 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.

[iemejia]

Run Spark ValidatesRunner

[iemejia]

Run Spark StructuredStreaming ValidatesRunner

[iemejia]

Run Java Spark PortableValidatesRunner Batch

[iemejia]

Run Python Spark ValidatesRunner

[iemejia]

Run Go Spark ValidatesRunner

[aromanenko-dev]

LGTM since it fixes a problem with an empty event log. But what's about original issue stated in BEAM-11213 ?

[iemejia]

I understood it more like a user friendliness issue but since this broke metrics on Spark History Server I preferred to go straight to remove the behavior, because history server is more important.