Add zap tooling to Docker container

[tl-sl]

Add ZAP tooling to docker container which allows for Zigbee apps that require ZCL clusters to be built (such as any of the example apps like Z3Light and Z3Switch). slc will automatically generate all required files from config/zcl/zcl_config.zap saved under the project src folder.

Snippet from .slcp file

config_file:
- path: config/zcl/zcl_config.zap
  directory: zcl

[puddly]

Interesting! Are you building end device or router projects with the firmware builder?

[tl-sl]

Yeh I am using it to build router firmware. Currently the zcl config is device specific, will probably need to extend manifest to set manufacturer/product strings here.

[puddly]

If you break the device model and manufacturer info out into a config/something.h file, you can set it using the existing c_defines: block.

[tl-sl]

If you break the device model and manufacturer info out into a config/something.h file, you can set it using the existing c_defines: block.

I initially thought of doing something like this, however ZCL configuration works different to the main project configurator.
The zap tool takes the config from zcl_config.zap (json file) and directly generates the required .c/.h header files. Unless I am missing something, there is no way override configuration using defines here, since the generated #defines are not wrapped in #ifdefs.

[puddly]

Ahh. Yeah, we don't currently have anything to modify JSON files. Perhaps something like:

json_config:
  - file: "config/zcl/zcl_config.zap"
    jq: |
      .endpointTypes[].clusters[].attributes[] | select(.name == "model name") 
      | .defaultValue = "some model"'

  - file: "config/zcl/zcl_config.zap"
    jq: |
      .endpointTypes[].clusters[].attributes[] | select(.name == "manufacturer name") 
      | .defaultValue = "some manufacturer"'

[puddly]

Sample implementation, untested: #85

[tl-sl]

I think that looks good, will test