* Simplify the convert script to same as generate script.
* Clean up the convert action.
* Fix the problem of binary build having a 0.0.0 version.
* Stop using package.json for runtime version detection, use .version.json instead.
* Fix the heap size for the binary executables.

* remove unnecesary checks for release workflow

* unit test for ZAP version being set

one of the stages (npm run self-check) was wiping out the binary version unintentionally.

* 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

chore: - change cypress check summary test

fix: - fix compiler-sfc warning

* remove unnecesary import

* verify artifact binary executable

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

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

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

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

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

Limiting the long strings to 253 for zigbee pr since the stack does not support attribute sizes greater than 255. However limiting the size for other stacks to 1024 for space conservation
JIRA: ZAPP-970

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.