- Fixing the count of mfg specific attributes such that it accounts for mfg specific attributes from mfg specific clusters
- Fixing the attribute_mask helper such that it creates a separation between zigbee and matter when creating the mask
- Fixing the attribute generation such that they have the mfg specific flag correctly
- Commenting a test for now to unblock zap builds
- JIRA: ZAPP-1077

JIRA: ZAPP-1036

- Extending all_user_cluster_generated_attributes to account for an attribute being a string or not
- Bumping the feature level pointer
- Cleaning up another query to get endpoint Id properly
- Adding the comma termination option for strings as well
- Updating existing helpers with more options
- Updating format_zcl_string_as_characters_for_generated_defaults to have isOctet and isCommaTerminated options
- Add in option to if_compare to check if one strings exists within another
- Update the zap-token version 2 zapt file and tests
- JIRA: ZAPP-1036

- Updated helper-tokens with token_attributes, token_attribute_clusters and token_attribute_endpoints helpers which can be used by the generation templates.
- Deprecated tokens_context and token_next helpers which were giving incomplete and wrong generation results
- Updated some existing block helpers in helper-zcl with token information to help with generation
- Added the queries for token helpers in query-attribute and query-cluster files
- Updated dbMapping with endpointTypeClusterExtended and endpointTypeAttributeExtended such that map functions can be used in a generic way
- Adding tests for token helpers
- JIRA: ZAPP-1036

Updating attribute and command queries to use packageIds such that custom extensions for standard clusters are handled appropriately

- When a cluster extension is added to standard clusters in the form of attributes or commands through custom xml then there is a need to account for packageIds
- For eg if a user adds a custom xml for the above use case and removes it the generation continues to generate for the added custom xml since it is not checking for removed packages.
- Github: ZAP#698

* chore: resolve conflicts

* chore: clean space

* chore: resolving conflict

* fix: fix duplicate issue after rebase

* chore: fix  typo issue and remove catch for duplicate function

Co-authored-by: A.ghasemkhani <a.ghasemkhaniii@gmail.com>

Switching to use templateUtil.ensureZclPackageIds instead of templateUtil.ensureZclPackageId to handle the custom xml generation which is not being accounted for currently when loading custom xml from the UI

Updating helper-endpointconfig, types and zcl-util to use packageIds instead of packageId to handle custom xml

- Updating one of the helper tests to have packageIds as well just like the packageId

Switching to packageIds in a session to resolve the custom xml addition use case

- Switching to packageIds in query-data-type-discriminator.js, zcl-loader.js to make sure we have the data type discriminators defined from standard xml for the custom xml
- Adding known packages to queries related to query-loader, zcl-loader-silabs to handle custom xml additions

Switching to packageIds and formatting the sql queries

Switching to packageIds for enums, bitmaps and structs such that custom xml additions are accounted for and removing cache for query-atomic because past testing in the local machine showed not using cache was faster.

Adding tests for custom xml generation

Updating api doc

Cleaning up function descriptions and fixing the test failures related to automaticallyCreateFields being called for undefined
Github: ZAPP#622

Switching to use ensureZclPackageIds instead of ensureZclPackageId for handling custom xml correctly in matter

Cleaning up docs and typos

Using dbApi.toInClause for the SQL IN clauses such that the queries don't break when we internationalize to different languages

Gihub: ZAP#622

Returning from insertDataType just like the other insert functions
Adding cluster id since it is being used by our code.
Removing dbcache usage since it seems to slow down the generation based on the following statistics
Upon generating z3Light app with dbcache: Average time taken across 5 runs: 24.8812
Upon generating z3Light app without dbcache: Average time taken across 5 runs: 19.272
These changes are saving around 5s locally
Adding the command argument count to the command queries to avoid additional sql calls for finding out the count within a block helper to reduce the complexity of the template
Bumping the feature level for zap
JIRA: EMZIGBEE-9385

JIRA: ZAPP-794

Making changes to an attribute query such that only reporting config default is generated for singleton attributes. Adding tests for the same using one of the existing zap files
JIRA: ZAPP-794

Align shared Cluster attribute/command configurations across endpoint for Zigbee
Within Zigbee, special rules apply when a cluster is enabled across multiple endpoints.
For the applied cluster, the attributes / commands configuration state are global across endpoints.
This behavior is toggled via
"generator": {"shareClusterStatesAcrossEndpoints": "true"} in SDK gen-template files.

BUG: ZAPP-715
Revert "minor query api cleanup", reverts commit 945a1546f6b5819f19c3b16a312fa9e98268446a.
bump featureLevel for cluster attribute/command generation diff between zigbee/matter (#500)

Align shared Cluster attribute/command configurations across endpoint for Zigbee

Within Zigbee, special rules apply when a cluster is enabled across multiple endpoints.
For the applied cluster, the attributes / commands configuration state are global across endpoints.
This behavior is toggled via 
"generator": {"shareClusterStatesAcrossEndpoints": "true"} in SDK gen-template files.

BUG: ZAPP-715

BUG: ZAPP-647

Ordering the queries with attribute.code, attribute.mfg_code instead of the inverse to get the order of attributes correct because we have attributes which do not have mfg code populated even though they belong to a mfg specific cluster for eg, global attributes. This was done because the order of attribute discovery changed if this change is not applied
JIRA: EMZIGBEE-7186

- 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

Adding mfg specific cases into the sql queries and adding back enabled incoming commands which was removed by mistake
JIRA: EMZIGBEE-7186

 Adding cluster mfg code to the queries such that manufacturing specific clusters, attributes and commands are accounted for correctly in the zap configuration
JIRA: EMZIGBEE-7186

Use max length for sizing the attribute store for attributes that are not strings and does not have a defined atomic size

- Instead of linking attributes to clusters which missed the global attributes from the queries changing the link to attribute->EP-attribute->EP-clusters->cluster such that global attributes are accounted for in zap config

Grouping by using attribute side because we have attributes names which are the same across different sides of the clusters.

- JIRA: ZAPP-653

BUG: ZAPP-356

This reverts commit 9d4f8bad.

JIRA: ZAPP-611

JIRA: ZAPP-611

JIRA: ZAPP-611