Fix headers types mismatch for OTLP Exporters

[sreejitkar]

Description

The said issue restricts the users from sending headers as tuples as the type signature is tightly coupled with the older version of OTLPExporterMixin.

Fixes #3209

Type of change

• Corrected the Type signatures of all OTLPExporters
• Removed header concatenation issue in the OTLPExporterMixin

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

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

• Ran Unitest for all Exporters and Mixins

Does This PR Require a Contrib Repo Change?

Answer the following question based on these examples of changes that would require a Contrib Repo Change:

• The OTel specification has changed which prompted this PR to update the method interfaces of opentelemetry-api/ or opentelemetry-sdk/

• The method interfaces of test/util have changed

• Scripts in scripts/ that were copied over to the Contrib repo have changed

• Configuration files that were copied over to the Contrib repo have changed (when consistency between repositories is applicable) such as in

  • pyproject.toml
  • isort.cfg
  • .flake8

• When a new .github/CODEOWNER is added

• Major changes to project information, such as in:

  • README.md
  • CONTRIBUTING.md

• Yes. - Link to PR:

• No.

Checklist:

• 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: sreejitkar / name: Sreejit Kar (64c04f0)

[sreejitkar]

Hi @srikanthccv , Could you please help me with the next steps for merge ?

[srikanthccv]

Thanks for the PR; It will be merged when it gets enough approvals without any pending comments.

[sreejitkar]

Looks like some checks are failing because of a bad SHA from the parent branch