adding mandatory endpointComposition data to XML for ZAP to consume (project-chip#34818)

* adding endpointComposition data to XML for ZAP to consume

* explicitly adding constraint as defined by the spec and defining compositions types

* fix composition type tag

* changing back to prevent both types being true which is not allowed

* explciitly setting conformance and contraint to account for all scenarios

Author: paulr34

src/app/zap-templates/zcl/data-model/chip/matter-devices.xml

@@ -2209,6 +2209,12 @@ limitations under the License.
         <deviceId editable="false">0x0070</deviceId>
         <class>Simple</class>
         <scope>Endpoint</scope>
+        <endpointComposition>
+            <compositionType>tree</compositionType>
+            <endpoint conformance="M" constraint="min 1">
+                    <deviceType>0x0071</deviceType>
+            </endpoint>
+        </endpointComposition>
         <clusters lockOthers="true">
             <include cluster="Identify" client="false" server="false" clientLocked="true" serverLocked="false"></include>
             <include cluster="Descriptor" client="false" server="true" clientLocked="true" serverLocked="true"></include>