Lambda Layer Update: OTel Python 1.12.0 & 0.33b0

[vasireddy99]

This PR updates the OTel Python Core dependencies to 1.12.0 and OTel Python Contrib dependencies to 0.33b0

Adding detail for PR build;
Executed the command tox in local and can verify both python3.8 , python3.9 are succeeded

Resolves :

• Remove protobuf pin when the fix is released in OpenTelemetry-python #269
  `

[NathanielRN]

We spoke offline and decided we do not want to jump the gun and release Python Lambda layers while the OTel Python SIG has them in pre-release. That is the case for 1.12.0rc1:

@vasireddy99 was able to pass the tests (and avoid the problem where conflicting versions like 1.11.0 are installed), by updating the CORE_REPO_SHA environment variable to point to the repo at the pre-release itself. Otherwise, it installs opentelemetry-test-utils at the specified commit and that package in turns pulls the latest stabe release of opentelemetry-api. Which is 1.11.0 right now.

We shouldn't release pre-releases because they are still being tested for bugs. For example consider this open issue with the latest 1.12.0rc1 release candidate 🙂

open-telemetry/opentelemetry-python#2716

[suqi]

Hello @NathanielRN @vasireddy99 , please help check again, OTel Python has released v1.12.0 officially several days ago.
https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.12.0

And if it cannot get upgrade, now my OTel lambda layer is reporting error

TracerProvider was missing force_flush method. This is necessary in case of a Lambda freeze and would exist in the OTel SDK implementation.

More detailed error info:

Thank you Team, have a good day!

[vasireddy99]

This PR will be updated to use 1.12.0 soon.

[Aneurysm9]

Is this still necessary?

[vasireddy99]

this env variable would be necessary to test against the specific commit other than main and is in a format the tests to follow the format of upstream

[NathanielRN]

Why do we need to do this?

[vasireddy99]

The usage of quotes is recommended by setup-python in gh actions. It would cause error when suppose a version 3.10 has to be used.