Model property in container will clash with exported field 'model' via a Content Fragment Sling Model Exporter

in certain cases a content fragment component needs to be represented as a Container to allow for inter-paragraph parsys injection.

Having a reserved property called model in the Container Props means that a Content Fragment component won't be able to leverage and extend from the default Container implementation due the property 'model' already being reserved for the PageModel object - see: thttps://github.com/adobe/aem-react-editable-components/blob/f61655af0e95bd9de4bf4d5769028a7c0883347f/src/components/Container.tsx#L31

Start with src/components/Container.tsx at the referenced model property and trace how Container Props are exported for the Content Fragment case described. Done means a Content Fragment component can extend the default Container while its exported model field no longer collides with the container properties.

Written by the indexing model from the issue text.