Update OTLP exporters to use HTTP instead of gRPC

[tokaplan]

Update OTLP exporters to use HTTP instead of gRPC

Changes

Please provide a brief description of the changes here.

Merge Requirements

For new features contributions, please make sure you have completed the following
essential items:

• CHANGELOG.md updated to document new feature additions
• Appropriate documentation updates in the docs
• Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

[cyrille-leclerc]

Thanks for starting working on this.

[cyrille-leclerc]

Is this comment desired or is it a development thing?

[cyrille-leclerc]

I think this env var is used by the Docker Compose:

opentelemetry-demo/docker-compose.yml

Lines 50 to 77 in 1e67b60

	ad:
	image: ${IMAGE_NAME}:${DEMO_VERSION}-ad
	container_name: ad
	build:
	context: ./
	dockerfile: ${AD_DOCKERFILE}
	cache_from:
	- ${IMAGE_NAME}:${IMAGE_VERSION}-ad
	args:
	OTEL_JAVA_AGENT_VERSION: ${OTEL_JAVA_AGENT_VERSION}
	deploy:
	resources:
	limits:
	memory: 300M
	restart: unless-stopped
	ports:
	- "${AD_PORT}"
	environment:
	- AD_PORT
	- FLAGD_HOST
	- FLAGD_PORT
	- OTEL_EXPORTER_OTLP_ENDPOINT=http://${OTEL_COLLECTOR_HOST}:${OTEL_COLLECTOR_PORT_HTTP}
	- OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE
	- OTEL_RESOURCE_ATTRIBUTES
	- OTEL_LOGS_EXPORTER=otlp
	- OTEL_SERVICE_NAME=ad
	# Workaround on OSX for https://bugs.openjdk.org/browse/JDK-8345296
	- _JAVA_OPTIONS

[cyrille-leclerc]

Is this comment removing the OTel Java Autoinstr agent from the Docker image? I think we need it