Fix Resource constructor examples to use Resource.create() (#4925)

* Fix Resource constructor examples to use Resource.create

Signed-off-by: Rohan Sood <rohansood10@users.noreply.github.com>

* retrigger CI

Signed-off-by: Rohan Sood <rohansood10@users.noreply.github.com>

* Fix Resource constructor in OTLP exporter examples

Address review feedback: also update Resource(attributes=...) to
Resource.create(...) in otlp-proto-grpc and otlp-proto-http exporter
module docstrings.

---------

Signed-off-by: Rohan Sood <rohansood10@users.noreply.github.com>
Co-authored-by: Rohan Sood <rohansood10@users.noreply.github.com>

Author: rohansood10

docs/examples/opencensus-shim/app.py

@@ -31,7 +31,7 @@
 
 # Set up OpenTelemetry
 tracer_provider = TracerProvider(
-    resource=Resource(
+    resource=Resource.create(
         {
             "service.name": "opencensus-shim-example-flask",
         }

docs/exporter/prometheus/prometheus.rst

@@ -27,7 +27,7 @@ Prometheus text format on request::
     from opentelemetry.sdk.resources import SERVICE_NAME, Resource
 
     # Service name is required for most backends
-    resource = Resource(attributes={
+    resource = Resource.create(attributes={
         SERVICE_NAME: "your-service-name"
     })
 

exporter/opentelemetry-exporter-otlp-proto-grpc/src/opentelemetry/exporter/otlp/proto/grpc/__init__.py

@@ -50,7 +50,7 @@
 
     # Resource can be required for some backends, e.g. Jaeger
     # If resource wouldn't be set - traces wouldn't appears in Jaeger
-    resource = Resource(attributes={
+    resource = Resource.create({
         "service.name": "service"
     })
 

exporter/opentelemetry-exporter-otlp-proto-http/src/opentelemetry/exporter/otlp/proto/http/__init__.py

@@ -50,7 +50,7 @@
 
     # Resource can be required for some backends, e.g. Jaeger
     # If resource wouldn't be set - traces wouldn't appears in Jaeger
-    resource = Resource(attributes={
+    resource = Resource.create({
         "service.name": "service"
     })