This reverts commit 61d328ca.

Fixing Custom XML issues:
- Cleaning up the custom xml UI update as well as the custom xml package uploading such that there are no duplicates
- Fixing the custom xml UI for attributes, commands and events when cluster extensions are added through custom xml. Needed the custom xml package ids to be included
- Fixing the duplicate attributes and commands which show up in the attribute and command UI when a custom cluster with custom attributes and commands is added. This is solved by using a set in : reduceAndConcatenateZclEntity(db, id, [...new Set([...standAlonePackageIds, clusterInfo.packageRef])],
- Adding unique constraint to Attribute table and adding insert or replace to attribute insert query such that custom cluster extensions are not reloaded into the db.
- Making sure the global attributes are part of the custom clusters in static-zcl.js while calling reduceAndConcatenateZclEntity
- Making sure that session partition numbering is correct for the partitionNumber column
- For loading custom cluster extensions such as attributes and commands. Making sure they are loaded into the database based on the top level zcl package loaded. This is needed for sdk upgrades or custom xml in multi-protocol. See changes to zcl-loader-silabs and zcl-loader
- When adding custom xml, there are instances where multiple zcl packages are loaded for the same xml file. This was an issue with the mutation observer. Getting the load new package call out of the observer to fix this. Reproducer: Open zap, add custom xml from extensions, close extensions pane, add another xml from extensions and you will see two instances of the xml added. If you add another xml then you see 3 instances. This is fixed in ZclCustomZclView.vue
- Making sure that the delete button appears across custom xml for removal and doing some minor UI cleanup
- Add more unit tests for custom xml
- Cleaning up zap toolbar UI for logos
- JIRA: ZAPP-1351

* changing session storage depending on what is given from parent iframe

* add stsApplicationId as a prefix to sessio uuid

* keeping session uuid code together

* PR review

* Revert "Fixing the theme based on the zcl package chosen (#1295)"

This reverts commit 5cc76149.

* Revert "Using getAllSessionPartitionInfoForSession instead of getSessionPartitionInfo for more stability (#1294)"

This reverts commit c9ca9f71.

* Revert "Fixing the ZAP GUI for blank configurations and opening category based configurations (#1289)"

This reverts commit fba76592.

* Revert "ZAP: Multi-protocol Configurator Integration (#1276)"

This reverts commit 06d14282.

JIRA: MCUDT-34394

Using getAllSessionPartitionInfoForSession instead of getSessionPartitionInfo for more stability (#1294)

JIRA: ZAPP-1350

* further cleanup and documentation

JIRA: MCUDT-34386

* get list from db instead of zcl.json

* bug fix - duplicating endpoints

* session partition reference needs to be what is selected in the query

> - Schema changes such that sessions now have session partitions to allow multiple zcl and template config files.
> - Session packages and endpoint types are now linked to a session partition such that generation and UI can be made exclusive to the device type selected on an endpoint
> - All relevant queries have been updated with session partition
> - imp-exp of .zap files is taken into account here as well
> - ZAP Generation can now generate the corresponding templates based on the category of the device type and the category of the generation templates eg: matter or zigbee. The same goes for UI
> - All existing tests pass with these changes
- Fixing the cluster view when multiple zcl device types are selected
- ZAP: Opening existing .zap files does not allow multi-device type selection
- Fixing sessionAttempt in initialize.js and cleaning up the packages from the session in jsonDataLoader function in import-json fixed this
- Other minor cleanup
- Fixing CMP generation for command line in startup.js#generateSingleFile such that it generates for all generation template json files and not just one of them
- bumping the feature level of zap
- Adding the reference to parentEndpointRef in endpoint extended in db-mapping due to rebase and also fixing the selectAllEndpointsBasedOnTemplateCategory for the same
- Cleaning up session package and session partitions to avoid having the wrong session packages and partitions in deleteAllSessionPackages
- Cleaning up query-session#ensureBlankSession
- Fixing the zap schema for command trigger warnings when adding endpoints
- Fixing the parent-endpoint.test.js just like the rest with session partition info
- Fixing the default attribute enablement based on catgeory such as matter/zigbee for global attributes
other minor cleanup
- Not showing the extensions tab in case of multi-protocol since it is currently not supported, see ZCLToolbar.vue
- Showing all logos based on the categories from the zcl files selected, see ZCLToolbar.vue
- Added multi-protocol tests, see multi-protocol.test.js, multi-protocol.zap, test-utils.js
- Removed lo-devices.xml from the zcl-with-extensions.json matter file to test multi-protocol more efficiently since for generation as is the case in reality as well.
- Fixing calls to insertEndpointType with device type params in query.test.js
- Fix cypress tests for vue tour which was happening due to category(zigbee/matter) not being picked from zcl properties files. Also handling the default use case when category is not found
- Calling this..dispatch('zap/updateClusters') in vue tour after update to endpoint type due to multi-protocol changes
- Fixing the default use case for showing and not showing UI elements in ui-options.js
- Fixing server-bare.test.js when inserting a package along with some other minor cleanup which is needed
- Fix the server-bare.test.js
- Improving the session creation and package selection process in the UI via ZapConfig.vue changes
- Pre-selecting the package files which exist in ZapConfig.vue. Also now showing package selection view if the packages which exist in the db are the same as the ones in the .zap file.
- Showing a warning in the custom xml page when a multi-proptocol config is open since custom xml is not currently supported for custom xml. See ZclCustomZclView.vue
- JIRA: ZAPP-1216

* Update XML with latest from Matter.

* Add initial unit test skeleton for the new ZCL files.

* Got all the new XML files to load in.

* Ignore the XML files which do not have an ID in cluster element.

* Propagate errors to the context from the new XML files.

* matter centric UI

* only allow selection of server if Matter project

* removing cypress tests because Zigbee and Matter GUI diverged - follow up task for separating them

* centralizing data

Some cleanup of the IDE integration code.

* tv-casting-app: ZAP generation js helper

* Update src-electron/generator/matter/darwin/Framework/CHIP/templates/helper.js

Commit suggestion by bzbarsky-apple

Co-authored-by: Boris Zbarsky <bzbarsky@apple.com>

Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 4.5.0 to 5.1.4.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.1.4/packages/vite

)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [axios](https://github.com/axios/axios) from 0.26.1 to 0.28.0.
- [Release notes](https://github.com/axios/axios/releases)
- [Changelog](https://github.com/axios/axios/blob/v0.28.0/CHANGELOG.md)
- [Commits](https://github.com/axios/axios/compare/v0.26.1...v0.28.0

)

---
updated-dependencies:
- dependency-name: axios
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Adding logic for configuring Parent Endpoint when user edits Endpoint

* cleanup, comments, and updating feature version

Code-generated tests have been removed, so there is no longer a "tests" type for
zap_regen_all.py.

* fixing helper to have a NULL placeholder and adding tests

* Phase 1 - Composite Endpoints

* 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