Add support for showing what profile a profileId corresponds to if the zcl.json includes a profilesCode xml

Silabs

Merge in WMN_TOOLS/zap from bug/overridingLargeAtomicTypeToPointerDeclarations/EMZIGBEE-8116 to silabs

* commit '990a8a90':
  Adding tests to check that asUnderLyingZclType helper returns pointer declarations for types which have size greater than 4 bytes
  Cleaning up the overridable functions JIRA: EMZIGBEE-8116
  Overriding 64 bit integers to uint8_t * - JIRA: EMZIGBEE-8116

Adding tests to check that asUnderLyingZclType helper returns pointer declarations for types which have size greater than 4 bytes

- Added an extra endpoint to an existing zap file to test the above
- Bumped the feature level pointer
- JIRA: EMZIGBEE-8116

JIRA: EMZIGBEE-8116

- JIRA: EMZIGBEE-8116

Silabs

Merge in WMN_TOOLS/zap from bug/endiannessRestrictionAbove8Bytes/EMZIGBEE-8121 to silabs

* commit '769b17cc':
  Adding tests for generated defaults in terms of endianness
  minor cleanup
  Preventing byte inversion for attribute defaults when size of attribute is greater than 8 bytes
  Preventing byte inversion for attribute defaults when size of attribute is greater than 8 bytes

- Testing for endianness with the as_generated_default_macro helper such that bytes are not reversed when size of attribute is greater than 8 bytes
- Adding a new zap test file and testing this via that
- JIRA: EMZIGBEE-8121

- JIRA: EMZIGBEE-8121

- Making changes to as_generated_default_macro helper such that the default values with size above 8 bytes do not have their bytes inverted between little and big endian
- JIRA: EMZIGBEE-8121

- Making changes to as_generated_default_macro helper such that the default values with size above 8 bytes do not have their bytes inverted between little and big endian
- JIRA: EMZIGBEE-8121

Fix the importing problem where the commands that are implemented by plugins are not enabled by default.

BUG: ZAPP-468

- Adding an argument to selectAllClustersWithIncomingCommands such that clusters can be grouped by either name or code. The reason for this is because there is cluster code collision when two manufacturing specific clusters have the same cluster id. Adding this option helps overcome that issue when dealing with command parser generation.
- Adding selectMfgClustersWithIncomingCommandsForClusterCode to retrieve manufacturing specific cluster details given the cluster code and adding the helper to retrieve this manufacturing_clusters_with_incoming_commands
- Add generation testing for the above work

- bumping the feature level pointer

- JIRA: ZAPP-605