Update end-to-end test server to implement resource detection scenario

[dashpole]

This PR:

• Fixes the resource detection module name
• Changes naming of resource detection functions to match semantic convention names
• Adds a zone/region function for app engine
• Falls-back to region when zone is not found (needed to pass resource detection tests).
• Implements the detectResource scenario.

The e2e test below passes the resourceDetection scenario.

[dashpole]

@aabmass where is "local" actually being run? It seems to be on GCP somewhere, as the metadata server is available, but it doesn't appear to be on GCE, since machine-type isn't being found as an attribute.

[aabmass]

@aabmass where is "local" actually being run? It seems to be on GCP somewhere, as the metadata server is available, but it doesn't appear to be on GCE, since machine-type isn't being found as an attribute.

It just connects to the local docker daemon, so in CI it's running on Cloud Build. We are also setting the network so that the inner container can get ADC

opentelemetry-operations-go/cloudbuild-e2e-local.yaml

Line 33 in 749b5ea

- --network=cloudbuild

See https://cloud.google.com/build/docs/build-config-file-schema#network.

[dashpole]

I ended up adding a function to detect when we are on GCE. That should help filter out other platforms (like cloud build) that we haven't implemented detection for.

[dashpole]

All passing now!