Feature: add support for chaincodeBuilderConfig

[arner]

Chaincode builders can use variables in their file contents. They're used by chaincode 'as a service to ensure the same packageID across different peers: fabric docs.

The Peer CRD supports adding a chaincodeBuilderConfig and so does the operator. But the API does not expose it, and it's not set in the deployment.

This feature would add the API to the swagger definition and update the peer deployment code. It should be fairly straightforward to add, and it would be helpful for anyone using 'chaincode as a service' on the open source Fabric images.

[arner]

If anyone who uses Ansible scripts to deploy the peers is reading this, in lieu of the feature you can also use the following task on an already deployed peer:

    - name: Apply patch to enable chaincodeBuilderConfig
      kubernetes.core.k8s_json_patch:
        api_version: ibp.com/v1beta1
        kind: IBPPeer
        namespace: "{{ namespace }}"
        name: "{{ organization_name }}peer"
        patch:
          - op: add
            path: /spec/chaincodeBuilderConfig
            value: "{\"peername\":\"{{ organization_name }}peer\"}"