[4.3] Create traits for the CMSObject error and property handling

[laoneo]

Summary of Changes

Split the CMSObject into traits so extension developers can already use them and remove their dependency from CMSObject. This pr is based on #38949 as it uses the exception trait.

The traits are deprecated so people will understand their code should be changes accordingly to the deprecate messages. In 5.0 the dependencies to CMSObject are removed from core then and do use the traits to ensure nothing will break in 4.

Testing Instructions

Load any back end view. CMSObject is used in tables and models so loading one of the views will use the CMSObject class.

Actual result BEFORE applying this Pull Request

All works.

Expected result AFTER applying this Pull Request

All works.

Link to documentations

Please select:

• Documentation link for docs.joomla.org:

• No documentation changes for docs.joomla.org needed

• Pull Request link for manual.joomla.org: Update new-deprecations.md for CMSObject Manual#50

• No documentation changes for manual.joomla.org needed

[laoneo]

@wilsonge and @nikosdion feedback is appreciated

[Abernyte-Git]

I have tested this item ✅ successfully on e993a85

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/39020.}

[nikosdion]

I am happy with this approach.

[obuisard]

Thank you Allon @laoneo for the PR