Elastic Search destination should not allow "none" auth method in Airbyte Cloud

[grishick]

It is currently possible to set up ES destination with authentication method = "none". This should not be allowed in Airbyte Cloud as it exposes publicly exploitable ES installations.

[VitaliiMaltsev]

@grishick i have two proposals on how to implement this task:
Proposal A
Remove "none" auth method from existing connector destination-elasticsearch and publish into the cloud
Pros and cons:

+ Easy to implement
+ No need to create separate connector
- We always need to enable auth security in elasticsearch setup even for local development 
- Potential backward compatibility issue for existing Airbyte cloud users

Proposal B
Create separate connector (e.g destination-elasticsearch-strict-encrypt) with disabled authentication method = "none" in spec
Pros and cons

+ We will have 2 similar but separate connectors for OSS and Cloud. For OSS version authentication method = "none" will be enabled
+ No worries of backward compatibility
- We should replace existing destination-elasticsearch connector with strict-encrypt version for Airbyte cloud
- All existing cloud users must create connection from the scratch  

[grishick]

@VitaliiMaltsev we have only 1 Airbyte Cloud workspace with ES destination, so let's go with proposal B which follows the same pattern as all other connectors