Continuous Loop and Database Error When Event Name Exceeds [EventName] Column Size Limit in [ExecutionPointer] Table

**Describe the bug**
Due to the size of the [EventName] column in the [ExecutionPointer] table, when attempting to write an event with a name exceeding 100 characters, an error occurs while trying to update the database. As a result, subsequent workflow steps continue to execute continuously in a loop.

**To Reproduce**
Attempt to write an event with a name that contains more than 100 characters.

**Expected behavior**
The background service should attempt to insert event details into the [ExecutionPointer] table, but when it encounters an event name that exceeds the column's size limit, it should handle the error gracefully and not enter into a continuous loop.

**Additional context**
This issue is particularly relevant for scenarios where event names are longer than the specified limit and need to be accommodated within the database schema.
[workflowCore.log](https://github.com/danielgerlag/workflow-core/files/12648300/workflowCore.log)

Reproduce the issue with an event name longer than 100 characters and inspect the ExecutionPointer table schema and the background service path that writes event details. Confirm that the database error is handled gracefully and that subsequent workflow steps do not continue executing in a loop.

Written by the indexing model from the issue text.