Removed issue with circular dependency on manual instrumentation.

[mlorenzana]

Description

Corrected issue on manual instrumentation where an environment variable is expected and if present creates a circular dependency.

Fixes #2056 #2744

Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A

Does This PR Require a Core Repo Change?

No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mlorenzana / name: Michael Lorenzana (c4b8e0a, 645f7cd)

[mlorenzana]

Unless I'm very mistaken, both these issues stem from manual instrumentation from a docker lambda.

In #2744, Docker lambdas do not require the same env vars as zip lambdas since you directly reference the handler method. Thus those variables are always empty when using a docker lambda.

In #2056, the circular dependency comes from assigning the handler to that env var, thus importing the same module twice (and in fact circularly).

In both cases, if the variable is left empty and the instrumentation code exits early, the issues will both be resolved.

[Kludex]

I'm not using docker, I'm using the Python runtime.