Cannot Delete Content types in current master.

[joseorsini]

As a follow up for #12716, additional tests made:

• Created a Test Content 001 Content Type, with only a Title Field.
• Under Large-1 Container on demo site, add this content type and print $!{title} value.
• Create a page using Quest - 1 Column.
• On Edit Mode, add a Test Content 001 content under the main container of this page. You should see printed the Content Title on this page.
• Attempt to delete the content type, which calls the destroy() method on ContentletAPI and then destroyContentlets() (the one that fails in regression tests). This shows on backend view:

• Go ahead and remove the Test Content 001 content from Large-1 container.
• Open again the page in Edit Mode. Content is still there, despite the container should not print contents from this content type. Nothing is printed from this content, though.

this is the current definition of container. See that Test Content 001 content type is not part of the code definition anymore:

• Try again to delete the content type. Same error as above

---

If we try to delete a content type like Call to Action, or the same content type above without following the steps for adding contents to pages/containers, we get this error

An unexpected system error occurred. 
com.dotmarketing.exception.DotDataException: An error occurred when  saving a system event with ID: [null]: Cannot find type adapter for  class 
com.dotcms.contenttype.model.type.ImmutableSimpleContentType

Stacktrace: https://gist.github.com/joseorsini/17f2fc375da89f52a503e9a4461817af

[joseorsini]

It makes sense that a content type deletion complains about an old container-contenttype relationship, however, it exists on an old version of the container itself (these relationships are versionable). Still, current live/working version of container does not reference this content type, so we should be able to delete the content type instead of going to each old version of the container and inspect which one refers to this content type.

Additionally, multi-tree relationships are not versionable, so if a current version of a container drops support for a content type, we shouldn't keep those records on this tree IMHO.

[jgambarios]

PR: #13242

[jgambarios]

By Wills request we reverted #13242 with this pull request #13255
We are waiting to the changes on this pull request #13193 to be merge in order to re-apply the changes made on #13242

[bryanboza]

Fixed, tested in the last master and now we are able to delete content types without problems

[DeanGonzalez]

Passed, had trouble dropping fields on a new content type, but will report that on separate issue.