* typescript
* do not check for github token when downloading from Nexus

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

* download from SiliconLabs fork by default
* enable Github token to be passed in via --githubToken

0. Add the workflow logic.
1. Remove some old muddle around project.env.DEV

* Share the ipc socket same way as single-instance shares sockets.

* Some code cleanup.

* Increase feature level to trigger IDE tests.

* Make server load both zigbee and matter data.

* Fix the hang of the generation in the client/server case.

* Automatically stamp versions at npm install time, to be ready for concurrency.

* Peg package-lock.json to the fake version as well.

* Add unit test for event field type checking.

* Update versioning scheme to on-the-fly inject a correct version for build.

* Add npm targets for version fake/real stamping.

* Update version-stamp with creating a real version in package.json

* Move a package.json logic to a function in script-util.

* Update printouts.

* When building, use a timestamp of a last git commit, NOT the current time.

* Export category and enable zapmatter target property.
* Add description to the zap file, so users can be presented with a nice dialog.

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

* Minor cleanup.

* Clean up some session creation in tests.

* Configure more lenient timeouts for github actions.

Adding helpers for zcl cli commands such that the right content is generated for Zigbee and other cleanup.

- Increasing the feature level pointer for apacka.json
- Checking for lowercase when querying bitmaps and enums since the atomics are in uppper case under certain occasions for eg BITMAP8 instead of bitmap8
- Getting rid of the cli helpers in helper-zcl.js and using the new data_type table after the schema change instead of the old logic. Also moving the cli helpers int helper-zigbee-zcl since it is specific to zigbee 3.0 only
- Adding helper-zigbee-zcl.js to template-engine such that the helpers are included
- Adding the new zcl cli helper in zap-cli.zapt such that testing of the new helper is covered along with the old one.
- JIRA: ZAPP-802

0. Downgrade typescript and downgrade quasar-cypress-testing-e2e, fix package-lock.
1. Peg cypress to correct version.
2. Update package-lock.json

0. Proper exit if passed zcl.json file is broken.
1. Make zcl.json files an array.
2. Fix unit tests, which do not pass an array to zcl files.
3. Clean up the API for multi-file loading.
4. Properly propagate array and load the packages.

* override Electron pop up dialogue to display Generate button correcty.

* fix Studio integration debug logging

* REST api, "/dirtyFlag", for getting user session's dirty flag.

* test rendererAPI's file open function in Cypress

* single build target for easier mac dev flow

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

0. Bring in an external single-instance package, that is not electron specific.
1. Add a util method.
2. Converge both headless and UI startup through the same logic.

This reverts commit 47d5e7a89c68851cd8e4521953cd975c4f26a96e.

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

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.

Github#510

0) Isolate some queries for the device types. Clean up the old device type helper.
1) Add ability to query for device type clusters.
2) Fix a loading issue and several query issues
3) Move device type queries to proper location.  Access device type subentities, and fix a loading bug.
https://github.com/project-chip/zap/issues/472
 - There were no helpers earlier that would allow access to clusters and attribute/command overrides in the device lists. Now there are.
 - There was a loading bug that didn't link the DEVICE_TYPE_ATTRIBUTE and DEVICE_TYPE_COMMAND properly back to ATTRIBUTE and COMMAND tables.
4) Add reasonable ORDER BY to a query.
https://github.com/project-chip/zap/issues/494
5) Add ORDER BY to a query.
https://github.com/project-chip/zap/issues/497
6) Properly convert database booleans into JS bools.
https://github.com/project-chip/zap/issues/496

JIRA: ZAPP-757

Adding helpers and cleaning up the code such that the new data type schema can be used for matter regen

- quer-data-type.js: Added selectSizeFromType to calculate the size of data types from the new data type table
- query-loader.js: Adding the reason for code falling into the else case. This happens when we have a cluster extension for a cluster which does not exist
- query-string.js: Adding a query to find the strings based on id
- helper-string-matter.js: This is a replica of StringHelper.js. Moving this file into the zap repo. There are other files which will need to be moved into the zap repo as well. Also deprecating helpers based on the naming convention for helpers
- helper-zcl.js: Adding the if_is_string helper which can be used by zap templates to detect if a type is a string or not.
- template-engine.js: Adding some error handling here
- type.js: Using the newly created queryZcl.selectSizeFromType instead of queryZcl.selectAtomicSizeFromType based on the new schema and getting rid of selectAtomicSizeFromType
- JIRA: ZAPP-757

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