At this point, the new data is not yet used, this simply adds the first part of the loading mechanism to deal with it.

* Add support for apiMaturity key in xml for cluster

* Add API maturity querying capabilities

* Add apiMaturity in the dtd for the zcl xsd

* Add more restrictions on api maturity type

* Ensure zap files contain the maturity level in them

* Fix typo

* Define a zap file that supports an api maturity test

* Start adding a unit test for api maturity

* Fix test file, prepare for client/server maturity test. Still broken unfortunately

* make unit test pass

* Remove description from struct

* Fix ordering to pass xml validation

* Minor update to force a CI re-run

---------

Co-authored-by: Andrei Litvin <andreilitvin@google.com>

- Add zcl_struct_items_by_struct_and_cluster_name helper for retrieving struct items based on struct and cluster name in helper-zcl.js
- Updating selectAllStructItemsByStructName to handle cluster name as well
- Updating the xml for TargetStruct such that it is now present in binding and access control clusters
- Adding a test to make sure the right struct items are generated based on cluster names
- Github: ZAP#916

* Cut down unnecessary repeat generations from same source.
* Break up zigbee tests into individual generations.
* Split database files.
* Fix the problem with the result.
* Clean up some custom package stuff.
* Consistently name tests.
* Add another generation for performance analysis.
* Add a full-th test for performance analysis.
* Sort out some nuances of the test.
* Separate each individual file for generation.
* There is no need to run Zigbee cypress tests twice.
* Support array for generateOnly option, and limit unit test generation to just what we test.
* Exclude more generations of things not needed for tests.
* Restore Matter test data to reasonably recent, and mandate the Matter tests to pass without errors.
* Add the all-clusters test for Matter.
* Bring back old matter XML files to keep Cypress fixtures happy.
* Comment out a code coverage. It was not doing much useful now, so we are commenting it out for now, until we restore it to correct functioning later, using the cache.

* Added code to enable EventList support for Matter.

 - Added new method to extract events from database: selectEndpointClusterEvents()
 - Added new helper functions to construct list (array) of supported event IDs:
   chip_endpoint_generated_event_count()
   chip_endpoint_generated_event_list()
 - Added eventList and eventCount entries to the EmberAfCluster struct
   in the generated endpoint_config.h file

The EventList data is treated similar to CommandList data.

The assumption is that events are always server --> client.

* Removed Unused eventMfgCodes variable in the collectAttributes() function

* Removed casting for generatedEvents in endpoint-config.zapt file

* Updated selectEndpointClusterEvents() function to use existing mapping method dbMapping.map.event

* Updated selectEndpointClusterEvents() to select all supported event types.

* removed unsupported select field in selectEndpointClusterEvents()

* https://github.com/project-chip/zap/issues/394


* Add showProfileId to ui options
* fix: change hide function name, fix cluster count issue

Co-authored-by: Mehrad Malayeri <mehrad.malayeri@gmail.com>
Co-authored-by: A.ghasemkhani <a.ghasemkhaniii@gmail.com>

Minor change to manufacturers file.

Add the data-driven logic for handling fabric-scoped and/or fabric-sensitive struct items and event fields. (#634)

0. Increase feature level.
1. Add logic to read fabricHandling from zcl.json
2. Act on data in the fabricHandling data key.

* Add fabric-scoped flags to schema.
* Add isFabricScoped to command loading
* Add fabric scope to command queries.
* Add fabric sensitivity to event queries.
* Add isFabricScoped to structs in XML, and load them correctly.
* Update queries with the fabric-scoped field for structs.
* Update schema diagram.
* Set events to being fabric-sensitive.

* Add unit test for event field type checking.

* Clean up some package queries and encapsulate db.

* Fix the loading of templates and zcl packages to include category and description.

* Increase feature level.

* Update generation templates handling with the new columns.

* Update preview and add the template name to the db.

* Update expected electron version to what we actually have.

* align command/attribute states if an endpoint's newly enabled Cluster is enabled on another endpoint as well.
* refactor naming
* remove useless import.
* clean up deprecated shareConfigsAcrossEndpoints flag via ZAPP-715
* unit test for zigbee flag existing in gen-template file.
* unit test for verifying Attribute Reporting tab being copied across endpoints

BUG: ZAPP-715

We had earlier some 6 months old "Matter test data", that was mostly Zigbee test data with a single CHIP cluster.
Matter had gone far ahead, and people who were just working with zap, without access to main Matter SDK repo,
were only testing with old data. So this updates all the metafiles for Matter and patches the unit tests to
reflect that.

- The type EUI64 was not being found because of inconsistency. we use small case when defining types at other places so changing to that
- Making sure that the zcl loader handles single character types without changing the case
- In the dotdot loader making sure we read the library.xml file before any of the other xml files
JIRa: ZAPP-757

Making changes required for implementing the new data type schema and making sure zap unit tests pass.

- Adding the discriminator to db-mapping. Also adding the query-data-type-discriminator for queries into the discriminator table.
- Making changes to the enum queries under query-enum to include size and other schema related changes
- Making changes to query-loader.js, query-zcl.js which reflect the changes required for the new data type schema
- Making changes to zap schema under zap-schema.sql to include the data_type_cluster table which is required to associate data types to clusters. Also adding some other constraints to other tables.
- Updating some content in helper-c and helper-zcl and overridable files
- Updating the zcl-loader-silabs.js and zcl-loader.js, zcl-loader-dotdot.js with respect to the new data type schema
- Updating all the test meta data files to define ZCLDataTypes for zcl.json files
- The test have been updated to account for the enum and bitmap data types which now go into the enum and bimap tables instead of the atomic table. So their counts have increased by 2 and 8 respectively.
- Some minor xml changes which were required for the zap unit tests because of the schema rework.

- JIRA: ZAPP-757

Updating the schema for ENUMS and BITMAPS and dealing with the query and data loading aspects based on the new schema

- Adding size to bitmaps and enums in db-mapping.js
- Updating the enum and bitmap queries as per the new schema in query-bitmap.js and query-enum.js
- Removing the duplicate tables in query-loader.js for enum_2 to enum and similary for bitmaps as well
- Updating the zap-schema.sql for data types
- Updating helpers in helper-zcl.js based on the new schema
- Using overridable.js to return the right data types for enums and bitmaps in ZUC
- Updating as_underlying_zcl_type helper such that it continues to return the same output as before with enums and bitmaps in zcl-util.js
- Cleaning up the old loading mechanism in zcl-loader-silabs.js. Also making sure that the types.xml file is loaded before the other xml files such that some data types do not have missing data type information. The types.xml ile has the atomic type definitions which need to be loaded before hand.
- Minor xml file updates
- JIRA: ZAPP-757

Adding the logic for the new ZCL Type schema. However some tables have been duplicated to conserve existing logic. The duplicate tables for enums, bitmaps and structs will be removed in subsequent commits

- Adding better error handling in db-api.js
- Adding the disciminator, data_type, number, string, bitmap_2, bitmap_field_2, enum_2, enum_item_2, struct_2, struct_item_2 tables which adds to the existing schema in zap-schema.sql
- Populating the above tables using the added changes in zcl-loader-silabs.js and query-loader.js. The trigger being used to create the above tables is through ZCLDataTypes defined in zcl.json
- Cleaning up xml
- JIRA: ZAPP-757

0. Add schema column.
1. Add loader logic.
2. Update zcl schema.
3. Update unit test files with example.

* unit test for shareConfigsAcrossEndpoints flag.

BUG: ZAPP-647

0. Enshrine privilege as an alias for role.
1. Update some script that was path sensitive.
2. Ignore generated package file.

- Adding sample extension xml to zap tests which has mfg specific clusters, attributes and commands
- Fixing cluster index for mfg specific generation
- Creating a zap file/configuration which has mfg specific clusters, attributes and commands for testing
- Adding zap-config related testing and the latest version of zap-config.h
- JIRA: EMZIGBEE-7186