* 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.

* Reordering of struct EmberAfAttributeMetadata members

* Test updated

* Adding alert mechanism which changes the button color when there are notifications to check

* removing debug code

* Adding a UI notification when commands are not available
* Updating test since there will be less number of characters when there is a label instead of an empty table
* Github#800

0. Add two zap files with intentionally wrong package paths, but correct categories.
1. Add a test that loads both matter and zigbee metadata.
2. Load a matter zap file and a zigbee zap file, and test that correct packages are attached.

* Proper renaming of a completely confusing function.
* Clean up the code a bit.
* Consider category as a most important criteria in the matching of packages.

* Remove a bunch of useless logic for loading validator.

* Clean up some mess of package loading, removing session where it is not needed.

* Update negative case.

* Fix the devserver execution for cypress.

* Make packageMatch a non-boolean option.

* Implement autoloading properly.

* Add a package matching mode which simply ignores the packages in zap file, used in unit tests.

* Clean up a unit test.

* Fix the matter test file to no longer point to zigbee.

* Simplify the analyze script.

* Update the template loader to not try to reload package options.

* Update docs.

* Clean up a comment.

* Remove unused argument.

https://github.com/project-chip/zap/issues/793

* Implement the initial selection of the valid sessions and property files.

Co-authored-by: Timotej Ecimovic <timotej.ecimovic@silabs.com>

Adding generic helpers with less hardcoding such that they can be used across different kinds of templates

- Adding selectStructsWithClusterAssociation which takes the logic src-electron/generator/matter/chip-tool/templates/helper.js#structs_with_cluster_name to the backend(sql query). structs_with_clusters helper uses this instead of exports.structs_with_cluster_name
- Updating cleanseLabelAsKebabCase so that it can be used instead of asDelimitedCommand
- endpoint type was being treated as signed integer due to parsing logic in zcl-silabs-loader.js. Added a separate condition for this
- Added generation tests for all the new helpers with an additional matter generation template
- Adding the groupByStructName option to structs_with_clusters to avoid duplicate rows
- Cleaning up the loader
- Cleaning up the helpers in helper-zcl
- For zcl data types, taking into account the signed attribute in the xml for numbers. If not mentioned then accounting for known exceptions such as single and double data types
Throwing an error in as_type_max/min_value when language option is not specified
Github: ZAP#679

- This solves the issue of zap generation when the saved zap file already has the custom xml reference and then generation is performed on it using cli
- Loading the main/standard gen template and zcl xml packages before the custom xml packages such that custom xml and clusters extensions within custom xml are loaded properly
- Fixing a query in query-package.js
- Adding tests for the above behavior by creating a zap file which has a reference to a custom xml. Testing generation of zap file and adding more tests for xml removal and generating again
- JIRA: ZAPP-971

* fix Nexus asset query issue.

was not constructing continuationToken URL correctly.

* ignore temp artifact files.

* unit test for download-artifact

* update cached download-artifact.js

* ignore download-artifact test from zap unit tests.

* download-artifact: add unit test / delegate to Github if specified branch is not cached on Nexus

intended for internal jenkins PRs that specifies a non-cached ZAP branch
on Nexus

Github: ZAP#698

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

- Handling the negative default values and float values for attributes correctly in terms of endianness(little/big)
- Testing as_generated_default_macro helper for negative and float values
- Adding valid hex values for testing
- Moving the util functions into type.js and resolving the endian issue for both zap-config and helper-endpoint templates
- renaming the functions since we use get for helpers
- Switching to DataView and ArrayBuffer to resolve the endianess for float and negative values
- Making changes to as_generated_default_macro helper which now handles endianness conversion for float, negative and string values
- Doing the same as above for longTypeDefaultValue.
- Cleaning up endian formatting code using dataView and other minor cleanup
- Reading from the right index when reading big endian formats in convertIntToBigEndian.
- When attribute size is greater than 4 then using an array buffer of size 8 such that there are no array offset issues when tackling negative integers
- CLeaning up typos
- Adding more tests
- Switching to BigInt for numbers outside the 4 byte range
- Cleaning up Code generation for long string attributes
- In helper-zcl#format_zcl_string_as_characters_for_generated_defaults, Accounting for 2 byte strings length and formatting it to little endian.
- In zcl-loader-silabs, making sure that max length for long strings is set properly when not mentioned correctly in the xml
- Adding tests for the changes in helpers.test.js
- Github: ZAP#509

* Generalize the JSON file inclusion.
* Add simple test for data gathering.

* Install glob package at toplevel.

* Separate file parsing from the file processing.

* Add globbing to the sdk.json

* Increase feature level.

* Increase required feature level in the test.

* Add the regen SDK apack action.

* Add index and directory name as possible replacements to globbing pattern generation.

* Give cleaner alias names to matter, so that we can change that on SDK as well.

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

* Remove some pointles wording from the test file.

* Upgrade cypress ubuntu to 22.04

* Add windows to cypress matrix.

* Change matrices for everything, because ubuntu 18 is becoming obsolete.

* Can not use windows until the scripts are fixed. Stupid.

* Condition Linux commands to linux.

* Add back the windows runners.

* Remove windows from OS matrix.

* Add more tests for better coverage of the Matter-related JS code.

This commit enables use of binary zap build for the Matter SDK. It bring the Matter JS code into the zap, cleans it up, and adds few new mechanisms to the templates.json files to support the Matter handling of yaml tests and test maintenance.

It also adds categorization and aliasing of helpers, so that only a subset can be loaded.

Furthermore, the handlebars instance is now no longer global, but it is created per-generation, and populated with the right subset of helpers.

Individual commits:

* Import: 07/29/2022
* Lint cleanup.
* Cleanup and alias few helpers.
* Add more directories to import.
* Use common aliases.
* Cleaning up imports.
* Import: add more files.
* Further imports cleanup.
* .js -> .ts
* Add category for Matter helpers.
* Comment, so I stop being confused.
* Add missing import of dbenum.
* Add the unit test for the helper loading via aliases.
* Fix the unit test.
* Cleanup the helpers api retrieval.
* Include a missing js file.
* Fix the api loading and testing.
* Skip automatic loading of categorized or aliased helpers.
* Add mechanism to auto-load helper categories and aliases.
* Make category functionality from gen-templates.json work correctly.
* Fix the bizarre mechanism of importing simulated clusters.
* Shortcut the package loading in case of only one available.
* Add more yaml files.
* Remove pointless directory read.
* Add the copying of the yaml files to copy script.
* Skip the meta symbol.
* Add the tests.
* Import: 8/2/2022
* Fix two small problems that accumulated into major problems.
* Fix various Matter issues.
* Remove stray require.
* Clean up the initialization API.
* Clean up the weird initialization of PICS.yaml.
* Remove a console.log
* Cleanup and alias another helper package.
* Add mechanism to share resource paths from gen-templates.json.
* Apply externalized resources to be able to remove all the yaml files.
* Remove yaml copying. Will not need this again.
* Import: 8/4/2022
* Detect open handles.
* Remove a useless test.
* Temporarily lower the coverage requirements, before we bring in Matter unit tests.
* Configure Matter code to stop doing ASI and instead put semicolons in the code.
* Move the tests out into JSON files.
* Move all the tests into ciTests json, deal with a more complex include+disable case.
* Properly read relative path for the tests.json files.
* Remove all tests code for matter.
* Remove unneeded JSON files that moved to SDK.
* Regen api baselines and remove references to test helpers.
* Stray rebase problem.
* Run cypress only once.

* fixing the dirty flag upon startup

* adding unit test which checks that the Dirty Flag is 0 upon empty configuration

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.

* Remove the wrapping of arguments in the generate scripts.
* Log gen execution to json file.
* Add gen log parser and uncomment the gen.log creation.
* Add skeleton of the regenerateSdk feature.
* Load ZCL packages.
* Load generation templates.
* Stop complaining about electron versions all the time.
* Add test SDK file and add a test entry point.

Long strings store their length in 2 bytes at the front of the string, with the
bytes being a little-endian representation of the string length.

But the endpoint config output was spitting out the length as big-endian, not
little-endian.  This caused things to be pretty confused and led to buffer
overruns trying to read data that was not there.

0. Add basic helper categorization.
1. Externalize handlebars instance.
2. Desingletonize the handlebars instance.
3. All handlebars instances are now taken from single location.

1) Remove struct_is_fabric_scoped and event_is_fabric_scoped now that we have
   isFabricScoped/isFabricSensitive on those objects.  Add the relevant XML
   attributes instead of trying to guess based on fields.
2) Remove event_fabric_idx_field and struct_fabric_idx_field, since we are no
   longer guessing based on fields.
3) Synthesize the relevant struct item or event field with the right name, type,
   field id, per spec, if the struct is fabric-scoped or the event is
   fabric-sensitive.

This is a hard requirement for implementing Leave events properly for Matter:
those have a fabric_idx field but are _not_ fabric-scoped.