[DEFECT] Content Type Copy Operation Fails for Legacy IDs (Non-UUID)

Problem Statement

Copying content types incorrectly rejects content types that have legacy numeric IDs instead of UUIDs, even though the copy operation generates a new UUID for the copied content type

The operation fails with the error message "ContentType 'id' if set, should be a uuid" if the source content type has a legacy numeric ID instead of a UUID format.

This validation is unnecessary because:

1. The copy operation creates a new content type with a new UUID (the source ID is set to null during copy)
2. The system already supports legacy IDs throughout the codebase
3. The validation prevents legitimate use cases where users need to copy older content types

Steps to Reproduce

1. Have a content type with a legacy numeric ID (non-UUID format)
2. Attempt to copy

Acceptance Criteria

The copy operation should succeed regardless of whether the source content type has a UUID or legacy numeric ID, since:
The copied content type will have a new UUID generated automatically

dotCMS Version

Latest, evergreen

Severity

Medium - Some functionality impacted

Start by locating the content type copy operation and the validation that emits "ContentType 'id' if set, should be a uuid". Reproduce the case with a legacy numeric source ID, then verify that copying succeeds and the new content type receives a UUID.