OTel source returns HTTP 500 for client-side protobuf validation errors instead of 400

[indrajababu]

When a client sends a protobuf request containing invalid UTF-8 in string fields
(e.g., InstrumentationScope name/version), the pipeline currently returns HTTP 500
with a generic error. This change returns HTTP 400 with a client-actionable message
explaining the issue.