Option to copy contentlet without copying relationships (MANY_TO_MANY / MANY_TO_ONE)

Summary

When copying a contentlet that has MANY_TO_MANY or MANY_TO_ONE relationships, dotCMS currently copies those relationships to the new contentlet by design. This enhancement request is to make that behavior configurable: allow users to optionally copy a contentlet without copying its relationships.

Current behavior

• ONE_TO_ONE / ONE_TO_MANY: relationships are not copied when copying a contentlet.
• MANY_TO_MANY / MANY_TO_ONE: relationships are copied to the new contentlet (same related contentlets are re-applied).

For MANY_TO_MANY and MANY_TO_ONE, there is no way today to create a copy that has no relationships.

Requested enhancement

• Add an option (e.g. checkbox or dialog choice) when copying a contentlet to copy without relationships.
• When that option is selected, the new contentlet should be created with no relationships, regardless of cardinality (including MANY_TO_MANY and MANY_TO_ONE).

This would support workflows where a user wants to duplicate a child contentlet (e.g. a banner) for reuse elsewhere without automatically re-linking it to the same parent(s) (e.g. carousel).

Reference

Support ticket: https://dotcms.freshdesk.com/a/tickets/35534

Start by tracing the contentlet copy flow and the relationship handling for MANY_TO_MANY and MANY_TO_ONE associations; the payload does not identify specific files or tests. Define where the copy-without-relationships choice is exposed and verify that selecting it creates a new contentlet with no relationships for every cardinality.