feat: migrate built in metrics to OTEL

[mutianf]

To use a custom otel instance:

/** Customer's application code */
SdkMeterProviderBuilder sdkMeterProvider = SdkMeterProvider.builder();

// resgister Builtin metrics
BuiltinViews.registerBuiltinViews("project-id", sdkMeterProvider);

OpenTelemetry openTelemetry = OpenTelemetrySdk.builder()
.setMeterProvider(sdkMeterProvider())
.setTracerProvider(..) // customer can set other providers
.build();

// pass in the openTelemetry instance
BigtableDataSettings settings = ..
   .setMetricsProvider(CustomOpenTelemetryMetricsProvider.create(openTelemetry));

Under the hood, BuiltinViews.registerBuiltinViews register the BigtableCloudMonitoringExporter:

registerBuiltinViews("project-id", sdkMeterProvider) {
    sdkMeterProvider
	 // register the metric reader
        .registerMetricReader(
            PeriodicMetricReader.create(
        // meter reader needs to be created with a exporter
                BigtableCloudMonitoringExporter.create(project, credentials)))
        .registerView(OPERATION_LATENCIES_SELECTOR, OPERATION_LATENCIES_VIEW)
}

[blakeli0]

Note that we recently started doing dependency governance, you would need to create a ticket for every new dependency. Once this PR is ready, please reach out to @suztomo regarding the exact process for OpenTelemetry dependencies, see a pilot example b/266431647.

[igorbernstein2]

I think you can do this now?