[BUG] Ensure execution proto message values are utf-8 compliant

[katrogan]

Describe the bug

The console fails to render executions with Request failed with status code 500 grpc: error while marshaling: string field contains invalid UTF-8 when an execution proto message contains invalid utf-8 chars

This ultimately came down to loading node_executions failed
api/v1/node_executions/flytetester/development/awh8z9wmnc5hlp687vdn?filters=&limit=2&sort_by.direction=ASCENDING&sort_by.key=created_at

We should ensure that proto messages are serializable over grpc and that the console doesn't hard fail loading executions in the project overview

Expected behavior

Invalid execution names shouldn't be accepted

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes