The AttributeDefinition for the 'content' attribute is sharing ADs for its fields with those created for the 'content' param to various deployment ops. This resulted in incorrect metadata as those fields have different "require" and "alternatives" settings in the two different use cases.

Besides being wrong data in the read-resoure-description this blocks WFCORE-2317 and WFCORE-2674 by introducing incorrect data that results in spurious validation that can't succeed.