* disabing default if storage is manually changed to external

* if Storage set to External the default field should be set to null along with not be editable.

* add comments and better descriptions of methods 

- Fixing the warnings which show up when disabling a cluster that is not required based on a device type.
- Adding tests for it
- Github: ZAP#1243

Github: ZAP#1094

slc not picking up zap due to arm64 vs aarch64 arhictecture naming convention. Not sure why we had arm64 in the first place. Need someone to review this. (#1234)

-Implemented optional save button, enabled by a query parameter and controlled by the dirty state
-Added listeners for cross-iframe messages
-Added notification to parent app when ZAP has finished loading

Show the tootip with path to the json files so that user can distinguish the packages when the name and description are the same (#1235)

JIRA: ZAPP-1288

* Adding the session notification messages with respect to Device Type specification:
- When a ZAP file is imported the spec compliance messages will be output into the console and will also be loaded into the session_notice table so that they can be viewed in the UI. See import-json.js
- When the user enables/disables the clusters, attributes or commands in the UI the sql triggers will check for compliance and remove the spec compliance messages from the session notification table if they are satisfied. See the sql triggers in the schema.
- Adding some color coding for session notice messages in the UI
* Adding the session notification messages tests:
- Adding a new zap file for testing spec compliance
- Adding the spec-check.test.js to test the above
- Adding additional test queries to test-query.js
- Fixing attribute tests to return the correct output counts in  query.test.js and importexport.test.js based on cluster side and not just the cluster itself as a whole which includes client and server
- Formatting the spec compliance message better for more readability on the console
-  Fixing the sql triggers for notifications in the case of clusters
- Minor cleanup
* Adding a polling mechanism for new notifications such that the UI can show the notifications coming from SQL triggers:
- Updating the sql schema with NEW_NOTIFICATION flag
- Creating a trigger on Session notice table which updates the new notification flag within session table
- Creating a polling mechanism in async reporting for session notice flag
- Updating db-mapping appropriately
- Update the schema
* Changing the schema such that triggers only log session notice warnings based on device type requirements:
* - Fixing the sql schema to delete messages appropriately
- Having the import spec check messages to show device type requirements as well
- Fixing the tests accordingly
* - Updating the schema to log cluster compliance messages to session_notice table
- Updating the import file logic to log cluster compliance messages to the console and session_notice table
- Adding the cluster compliance message tests apart from the device type compliance message tests
- Cleaning up importEndpointTypes
- Github: ZAP-1194

Adding more logic to pick a better package before picking up the first package in the list of available packages (#1233)

- Using the zcl and templates json file which is passed as arguments by UC when a file within the .zap file is not found as part of the fuzzy logic. This makes sure that zap is not picking template files from different sdks during the initial project creation and generation
- Adding more logic to pick a better package before picking up the first package in the list of available packages
- Minor cleanup

* Fix some security issues.
* Add the UI element that will toggle the functionality of IDE component toggling.
* Deal with the back-end changes for the manual component toggling override.

- The changes to import-json.js allows the ZAP UI to load instead of throwing an error and locking ZAP.
- Now the error message appears in the ZAP notification's pane so that the user can see a detailed error and act upon it
- Minor cleanup
- JIRA: ZAPP-1148

At this point, the new data is not yet used, this simply adds the first part of the loading mechanism to deal with it.

zapTypeToClusterObjectType needs to be consistent with the actual types we
generate for cluster objects, and it was producing different output for a struct
(or event) which had an all-caps name.

* Eliminate some TS leftovers.
* Remove some old junk.
* Lower the thresholds temporarily.
* Add conditionality for regen tests.
* Fix conditionality of zigbee regen test.
* Clean up some code.

* disabling buttons if forced external (MatterSDK)

* fix about page bug

* update dependencies

* cleanup

* PR review

* update electron builder

* add mrpActiveThreshold value and ICDOperatesAsLit to the simulated DiscoveryCommandResponse

* update name

* remove cleanDb

* Further takedown of the TS files.

* Clean up a unit test.

* Clean up imports in tests.

We treated things with neither "introduced" nor "provisional" annotations as
provisional in availabilityHelper(), but isProvisional() returned false for
them.  This could lead us to generate non-provisional code (conditioned on
isProvisional()) that would try to call into things with provisional
availability, which would fail to compile.

The fix is to make isProvisional the source of truth for whether things are
provisional, move the "no introduced annotation" check into isProvisional, and
factor out the "have provisional annotation" logic so we can keep having the
warning when we take the "provisional because not otherwise annotated" codepath.

* add custom file type to open file dialog

* Modify zcl extension popup style

* Modify btn position and fix hover style

Also fixes endpoint-config codegen for the device type array: These are 32-bit
values, not 16-bit.

* query the attributes with the edited global attributes

* Add support for apiMaturity key in xml for cluster

* Add API maturity querying capabilities

* Add apiMaturity in the dtd for the zcl xsd

* Add more restrictions on api maturity type

* Ensure zap files contain the maturity level in them

* Fix typo

* Define a zap file that supports an api maturity test

* Start adding a unit test for api maturity

* Fix test file, prepare for client/server maturity test. Still broken unfortunately

* make unit test pass

* Remove description from struct

* Fix ordering to pass xml validation

* Minor update to force a CI re-run

---------

Co-authored-by: Andrei Litvin <andreilitvin@google.com>

* Fixing endpoint type command table schema

- incoming and outgoing used to be in the endpoint_type_command table as a single record. However this is an association that is related to the command source and the cluster side. When the cluster side is the same as the command source then it is an outgoing command. If the cluster side and command source are not the same then it is an incoming command. Now we have 2 entries instead of 1 in the endpoint_type_command based on this logic.
- The above allows us to implement the enabled only .zap file correctly or else we lose the incoming commands when the .zap file is saved for the enabled only content since the way the commands were stored before this commit is that the client sourced commands were stored in the client side cluster and the server sourced command is stored in the server cluster which was wrong.
- Updating the endpoint_type_command queries based on the schema changes to the table
- Fixing the import/export for the above schema changes
- Updating the UI code to capture the new schema correctly
- In the insert command for ENDPOINT_TYPE_COMMAND table in query-impexp.js there is an ignore because the .zap files have been hand edited where there are multiple references of the same command in it.
- Adding generation tests for the enabled only file format
- Updating the default zap file format version to 2
- JIRA: ZAPP-1113

NOTE: for zap-cli binary, the mac x86 binary is used for the arch64 package
      as a workaround since pkg, the build tool, does not official support for mac-arch64 yet.

* make sure session create is async