Add support for disabling TLS

[rohanshah18]

Problem

Add support for enabling/disabling TLS.

Solution

Added enableTls boolean flag which is set to true by default but when set to false, it will be disabled.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Infrastructure change (CI configs, etc)
• Non-code change (docs, etc)
• None of the above: (explain here)

Test Plan

Since the flag is set to true by default, the existing integration tests should work as it is.

[haruska]

Couple considerations:

1. Is this TLS flag needed? In the example code:

pinecone-java-client/src/main/java/io/pinecone/configs/PineconeConfig.java

Lines 30 to 38 in da7ebc2

	* // Custom channel with timeouts
	* try {
	* builder = builder.overrideAuthority(endpoint)
	* .negotiationType(NegotiationType.TLS)
	* .keepAliveTimeout(5, TimeUnit.SECONDS)
	* .sslContext(GrpcSslContexts.forClient().build());
	* } catch (SSLException e) {
	* throw new PineconeException("SSL error opening gRPC channel", e);
	* }

It looks like you can set negotiationType(NegotiationType.PLAINTEXT) to turn off TLS?

2. Is the flag really global to PineconeClient? Or is it per-connection to an index?
3. Another example had the host with a http(s):// prefix and :PORT suffix. Would the http vs https prefix on the host be enough without setting a specific flag? Or is this considered bad practice?

[rohanshah18]

Couple considerations:

1. Is this TLS flag needed? In the example code:

pinecone-java-client/src/main/java/io/pinecone/configs/PineconeConfig.java

Lines 30 to 38 in da7ebc2

	* // Custom channel with timeouts
	* try {
	* builder = builder.overrideAuthority(endpoint)
	* .negotiationType(NegotiationType.TLS)
	* .keepAliveTimeout(5, TimeUnit.SECONDS)
	* .sslContext(GrpcSslContexts.forClient().build());
	* } catch (SSLException e) {
	* throw new PineconeException("SSL error opening gRPC channel", e);
	* }

It looks like you can set negotiationType(NegotiationType.PLAINTEXT) to turn off TLS?

2. Is the flag really global to PineconeClient? Or is it per-connection to an index?
3. Another example had the host with a http(s):// prefix and :PORT suffix. Would the http vs https prefix on the host be enough without setting a specific flag? Or is this considered bad practice?

1. Yes, we set negotiationType(NegotiationType.PLAINTEXT) to turn off TLS. This is where the flag is used: https://github.com/pinecone-io/pinecone-java-client/pull/150/files#diff-b976ef187206eaaba2d35fc19f368cbc2674b74e86ac31b75e0e969378d4608dR142
   If I were to not use the flag, how can I know whether we want to turn on or off the TLS?
2. We have a config object which is instantiated when a pinecone class is instantiated. And the same config object is further used for Index class which is responsible for gRPC index connections.
3. I'm not sure if I understood pt#3 but I'll go ahead and explain how we handle the host. The flag is enabled by default so tls is enabled and hence when trying to establish gRPC connection, we actually format the host by ignoring http(s) here:
   

   pinecone-java-client/src/main/java/io/pinecone/configs/PineconeConnection.java

   Line 183 in da7ebc2

   public static String formatEndpoint(String host) {

[ssmith-pc]

Looks straightforward, few minor comments