config.js validateProfile is confused about how to be insecure

[cburroughs]

In validateProfile of config.js we have:

        assert.optionalBool(profile.insecure,
            profile.name === 'env' ? 'TRITON_INSECURE or SDC_INSECURE'
: 'profile.insecure');

However, this is the only occurrence of TRITON_INSECURE. Everywhere else uses TRITON_TLS_INSECURE

[trentm]

https://cr.joyent.us/#/c/6116/

[trentm]

This will be in the next release (I belive there are coming rbac-y changes, so I won't cut a release just for this).