Connecting to a gateway using an environment locally sets ssl overrides incorrectly

[liam-grace]

An environment file supports setting the parameter ssl_target_name_override in each node
e.g.

 {
        "name": "peer0.org1.com",
        "api_url": "grpcs://0.0.0.0:9051",
        "type": "fabric-peer",
        "msp_id": "Org1MSP",
        "pem": "LS0tLS1CRUdJTiBDR",
        "wallet": "Org1",
        "identity": "admin",
        "ssl_target_name_override": "peer0.org1.com"
    },

And a CCP supports the same parameter, in a different format e.g.

...
"grpcOptions": {
    "ssl-target-name-override": "peer0.org1.com"
}
...

The extension, when using a gateway created using an environment config, instead creates a CCP that looks like

...
"grpcOptions": {
    "ssl_target_name_override": "peer0.org1.com"
}
...

Possible Fix

Change the case format of the 'ssl_target_name_override' in the generated CCP to 'ssl-target-name-override