[frontend] Always log CheckEventBlobSizeLimit violations

[3vilhamster]

What changed?
Always log details on CheckEventBlobSizeLimit violations and failWorkflowIfBlobSizeExceedsLimit.

Why?
It is the only source that can point domain owners to specific workflow failures. Metrics do not have a workflow-id dimension, so we rely on logs to find exact workflows.
These operations lead to failure of either a workflow or request (in case of query) or data truncation - in case of activity failure result. Having too many of these violations is unexpected, and it should be easy to point customers to specific workflows.

How did you test it?
unit tests

Potential risks
If there are customers that have a lot of workflows with failures, we can bloat logs.
However, even in Uber's case, these violations are rare - since they are failing workflows.

Release notes

Documentation Changes

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.77%. Comparing base (95ba44c) to head (1f1b271).

Additional details and impacted files

Files	Coverage Δ
service/frontend/api/handler.go	65.27% <100.00%> (ø)
service/history/decision/handler.go	94.93% <100.00%> (ø)

... and 6 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 95ba44c...1f1b271. Read the comment docs.

[jakobht]

Looks good. Maybe we could do something in the client? But this at least improves the situation.