Zigbee pro does not support long strings since attribute_largest macro has a limit of 255 based on the rest of our code

- Limiting long string attribute size to 253 because of functionality not available and this is breaking the application builds
- JIRA: ZAPP-970

- 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

* add pack:mac:native target
* workaround macOS Jenkins machine not able to build mac universal image.
* workaround for download-artifact build issue on node14, until DevOps can upgrade node16

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

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

* support to list latest artifacts on Github via '--nameOnly'
* fix function call bug.

* 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

* build universal mac image for x64/arm64.

using 'exec' to launch electron-builder as a workaround for npm launch bug.
relying on npm/npx launch will cause electron-builder to hang

* trigger mac cert setup conditionally.

Dirty-flag:
* Remove dirty flag logic from "studio-rest-api" area, since it really has nothing to do with Studio REST API.
* Add a new file for it.
* Clean up the annoying error that kept printing upon shutdown.
* The dirty-flag reporting is now a generic async reporting mechanism, with dirty flag as an example.

Cypress:
* Collapse the two uitest scripts.
* Replace electron with chrome for cypress runs.
* Disable two validly failing tests.

* https://github.com/project-chip/zap/issues/553
* https://github.com/project-chip/zap/issues/557
* https://github.com/project-chip/zap/issues/556
* https://github.com/project-chip/zap/issues/570
* https://github.com/project-chip/zap/issues/532
* https://github.com/project-chip/zap/issues/527


* test: update check_summary tests
* fix: check for undefined zclProperties

Co-authored-by: Pedram Kashani <kpedram@terafastnet.com>
Co-authored-by: A.ghasemkhani <a.ghasemkhani@gmail.com>

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

* convert assset dl script to typescript.

* dl assets from official nexus repo

* remove  octokit debug

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.

* fix enabled clusters test file

* adding ci for cypress against matter data

* updating cypress.json

* fix runtime error.

* printout exact Nexus download src folder addr

* fixing the dirty flag upon startup

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

Minor change to manufacturers file.

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

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.