Remove TLS support from firehose receiver

[wu-sheng]

Notice, no HTTPS/TLS setup support. By following AWS Firehose request, it uses proxy request (https://... instead of /aws/firehose/metrics), there must be a proxy(Nginx, Envoy, etc.).

• If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
• Update the CHANGES log.

@pg-yang I think we need to update Firehose and S3 document to add a proxy requirement in the metrics forward path

[wu-sheng]

Upstream discussion on Armeria to locate this.

https://line-armeria.slack.com/archives/C1NGPBUH2/p1676811880163349

[wu-sheng]

Debug logs from @pg-yang

[pg-yang]

We should remove the configurations from

skywalking/oap-server/server-starter/src/main/resources/application.yml

Lines 558 to 560 in cabe40e

	enableTLS: ${SW_RECEIVER_AWS_FIREHOSE_HTTP_ENABLE_TLS:false}
	tlsKeyPath: ${SW_RECEIVER_AWS_FIREHOSE_HTTP_TLS_KEY_PATH:}
	tlsCertChainPath: ${SW_RECEIVER_AWS_FIREHOSE_HTTP_TLS_CERT_CHAIN_PATH:}

as well

[kezhenxu94]

Configs in yaml file should be removed too

[pg-yang]

And configuration-vocabulary.md

[kezhenxu94]

And doc https://github.com/apache/skywalking/blob/cabe40eb47fc83d681f1f40359798915f8ff7428/docs/en/setup/backend/aws-firehose-receiver.md#notice

[wu-sheng]

Debug logs from @pg-yang

And doc https://github.com/apache/skywalking/blob/cabe40eb47fc83d681f1f40359798915f8ff7428/docs/en/setup/backend/aws-firehose-receiver.md#notice

I will update other docs, and leave AWS doc to @pg-yang. He should have a more accurate version than I could do.

[pg-yang]

LGTM, wait for GHA