Verify encoding option behavior

[binarylogic]

We need to verify the encoding option behavior across sinks to ensure it's consistent and not confusing:

• aws_cloudwatch_logs sink has an encoding option that accepts text and json
• aws_cloudwatch_logs sink does not require a value for encoding and dynamically encodes each event based on it's implicit/explicit structure
• aws_kinesis_data_streams sink has an encoding option that accepts text and json
• aws_kinesis_data_streams sink does not require a value for encoding and dynamically encodes each event based on it's implicit/explicit structure
• aws_s3 sink has an encoding option that accepts text and ndjson
• aws_s3 sink requires the encoding option to be set, it does not perform any dynamic encoding.
• console sink has an encoding option that accepts text and json
• console sink does not require a value for encoding and dynamically encodes each event based on it's implicit/explicit structure
• elasticsearch sink does not have an encoding option since it must be encoded via JSON
• http sink has an encoding option that accepts text and ndjson
• http sink requires the encoding option to be set, it does not perform any dynamic encoding.
• kafka sink has an encoding option that accepts text and json
• kafka sink does not require a value for encoding and dynamically encodes each event based on it's implicit/explicit structure
• splunk_hec sink has an encoding option that accepts text and json
• splunk_hec sink does not the encoding option to be set, it performs dynamic encoding.
• tcp sink has an encoding option that accepts text and json
• tcp sink does not require a value for encoding and dynamically encodes each event based on it's implicit/explicit structure