Add support to type bytes for OTLP AnyValue encoding

[wasup-yash]

Description

Fixes #4118

Type of change

• New feature (non-breaking change which adds functionality)

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 Contrib Repo Change?

• 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: wasup-yash / name: Yash sharma (750180c, 621d8b2, 995d5fc, badcb13, 95de5e9)
• ✅ login: lzchen / name: Leighton Chen (6bd95f8, dfa6e90, 5b42a7e)

[wasup-yash]

@lzchen tagging for the review if good then can proceed to merge

[emdneto]

Thanks. Care to add a changelog entry and update an existing test or add a new one?

[wasup-yash]

Thanks. Care to add a changelog entry and update an existing test or add a new one?

did the entry part, but couldn't find the test specifically for the encoding part, can you point me to exactly where are we testing for the encoding formats?

[lzchen]

@wasup-yash

Please mark this as PR if it is ready to review.

[wasup-yash]

@wasup-yash

Please mark this as PR if it is ready to review.

done

[lzchen]

@wasup-yash

You can either add a new file here creating a test suite to just test encode_value or you can add to the existing encode_attributes test suit to include these uses cases.

[wasup-yash]

what could be the reason tests are failing, is it cause the tests are not written correctly? (I am not familiar with the tests written in Python so If anyone can suggest what needs to be done here )

[lzchen]

@wasup-yash

Left a comment on how to fix your test.

Also, please add a CHANGELOG entry.

[xrmx]

@wasup-yash Need to run black over your changes and add a CHANGELOG entry, I suggest to setup pre-commit as in CONTRIBUTING.md to have it done automatically at commit time.

[wasup-yash]

Need to run black over your changes

what does it mean though , understood the pre-commit part though

[zhihali]

About the black and the isort, check the contribution.md here

opentelemetry-python/CONTRIBUTING.md

Line 62 in 110bb73

`black` and `isort` are executed when `tox -e lint` is run. The reported errors can be tedious to fix manually.

and about the changelog entry, you can refer to some merged PR, how they write the changelog. A randome example: #4122

[wasup-yash]

Do I have to run pre-commit run --all-files and then commit the changes as there were a lot of changes ? cause this time I did just only , a pre-commit install and then committed the changelog.md and there were 3 skipped files by pre-commit that was it :)