* "clusterSize:" had a stray ':' that was causing generation to produce invalid
  output.
* The old code had things indented sanely, and this is just restoring that.
* There was no detection of unknown tokens, which would have quickly caught the
  "clusterSize" problem.

- Fixing Token Attribute helpers to include cluster defines
- Sorting token endpoints by endpoint id
- Bumping the feature level pointer
- JIRA: ZAPP-1085

Device types are 32-bit in the spec.

* Restore one matter unit test to being operational.
* Allow for sorting and omitting certain items in the struct population.
* Increase feature level.

- Changing the default order of endpoint_attribute_list to what it was such that previously released SDKs continue to build their apps seamlessly. Newer templates can mention this order within the template itself
- fixing the endpoint_config test to default to old order
- JIRA: ZAPP-1081

* Extract the reporting into an array before laying out into a struct init line.
* Add a unit test for reporting generation.
* Allow parametrized reordering of reporting configuration struct elements.
* Parametrize the attribute list struct item ordering.
* Parametrize min/max struct order for the reporting helper.
* Another ordering issue.

- Throwing a warning in the notifications page of the zap UI instead of throwing an error in template-engine such that we backwards compatibility can be maintained
- Changes to helper.js files have been made to fall back to old way of implementation in the case of global.resource([key]) not finding the data required
- Github: ZAP#941

- 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

Updating the zap file and tests because the NVM settings in the application were not in sync across endpoints and this was causing indeterministic results (#931)

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

* Add a test file for this case
* Properly handle the custom package ID regardless of whether it has been loaded or not before.

* Use a single Matter config yaml instead of per-list yamls or hardcoded lists.

* isWeaklyTypedEnum removal is on purpose.

* 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()

* Upgrade Quasar to v2 and Vue to v3.
* Upgrade Cypress and Jest tests.
* Extend license whitelist.
* Temporary hide Vue Tour.

- These changes allow data types having the same name belonging to different clusters to be loaded.
- The queries have been modified such that cluster specific data types are searched for and inserted into the DB. If not found then generic data types which do not specifically belong to a cluster are used.
- The changes have been applied to enums, bitmaps and structs and then corresponding changes have been made to enum_items, bitmap_fields and struct_items
- Extracting the cluster codes correctly in zcl-loader-silabs.js such that it can be used in query-loader.js
- Updating the requiredFeatureLevel such that the stacks can use the new feature level if templates change according to these changes
- Github: ZAP#906

This allows variables like $CHIP_ROOT to be used, which is needed when
the chip codebase is a submodule of the repository the zap file is in.

Throw an error when any variable used fails resolving.

It would get things wrong if two different clusters had a response command with the same name.

There were two bugs:

1) asMEI produced incorrect output if the manufacturer code was high enough that
   the high bit in it was set, due to ending up with negative numbers.
2) chip_server_clusters for some reason used mfgCode, not manufacturerCode
   (which almost everything else uses).

pass in correct deviceTypeRef and filter by matching cluster id

* Reordering of struct EmberAfAttributeMetadata members

* Test updated

So if a cluster is removed, everything in that cluster should be
considered removed.

Move it to a YAML resource file provided by the template instead.

* Add temporary target used to test with local fork of pkg.

* Honor ZAP_SKIP_REAL_VERSION environment variable.