Start child with WorkflowID longer than 255 with SQL as persistence would stuck

[yiminc]

Due to DB column size limit, the workflow ID length limit is 255 when using SQL as persistence layer.

If a workflow try to start a child with workflow ID longer than 255, the workflow would see a child initiated, and then it would stuck. Server log indicate that it is stuck in the start child transfer with error like "msg":"Operation failed with internal error.","error":"createOrUpdateCurrentExecution failed. Failed to insert into current_executions table. Error: pq: value too long for type character varying(255)","error-type":"serviceerror.Unavailable"

This is bad from user experience POV. At least it should fail the child sooner with clear error.

[yycptt]

We have limit.maxIDLength but that's a dynamic config and people may not have the right config for SQL causing this issue to happen.

I think either the maxIDLength should not be a dynamic config, but hardcoded valued based on the persistence implementation used. Or we need to enforce a max limit based on the persistence impl used.