Improve data integrity errors handling for dotCLI push operations

Problem Statement

In dotCLI, when users push changes that involve advanced modifications—such as altering fields like clazz, dataType, or fieldType directly through the API, there can be data integrity issues if invalid values are used. These issues can lead to system errors or corrupt data, which are not currently handled with clear or helpful error messages. Improving the error handling for these cases is critical to maintaining data integrity and providing users with actionable feedback.

Steps to Reproduce

Use dotCLI to make advanced modifications to a content type, such as changing the clazz, dataType, or fieldType fields.
Push these changes through the API using dotCLI.
Observe that if invalid values are used, the system may either throw unclear errors or allow the data to be corrupted.

Acceptance Criteria

Enhanced Error Handling: Ensure that dotCLI provides clear, actionable error messages when invalid values are used for fields like clazz, dataType, or fieldType.
Data Integrity Checks: Evaluate if we can Implement checks to prevent invalid data from being pushed, ensuring that all modifications conform to the expected schema and data types.
Consistent Error Messaging: Error messages should be consistent across different types of invalid modifications, guiding users on how to correct their input.

dotCMS Version

Tested on [ trunk_78bb755 ] // Docker // dotCLI

Proposed Objective

Quality Assurance

Proposed Priority

Priority 2 - Important

dotCMS / core