[Dev] Support opentelemetry cpp

[lshmouse]

Description

Add

bazel run -c opt @io_opentelemetry_cpp//examples/grpc:server_grpc 
ERROR: /home/qcraft/.cache/bazel/_bazel_qcraft/e1d25c724e0056022d92d7bdfe62b271/external/bazel_tools/platforms/BUILD:89:6: in alias rule @bazel_tools//platforms:windows: Constraints from @bazel_tools//platforms have been removed. Please use constraints from @platforms repository embedded in Bazel, or preferably declare dependency on https://github.com/bazelbuild/platforms. See https://github.com/bazelbuild/bazel/issues/8622 for details.
ERROR: /home/qcraft/.cache/bazel/_bazel_qcraft/e1d25c724e0056022d92d7bdfe62b271/external/bazel_tools/platforms/BUILD:89:6: Analysis of target '@bazel_tools//platforms:windows' failed
ERROR: /home/qcraft/.cache/bazel/_bazel_qcraft/e1d25c724e0056022d92d7bdfe62b271/external/io_opentelemetry_cpp/sdk/src/common/platform/BUILD:17:11: errors encountered resolving select() keys for @io_opentelemetry_cpp//sdk/src/common/platform:fork
ERROR: Analysis of target '@io_opentelemetry_cpp//examples/grpc:server_grpc' failed; build aborted: 
INFO: Elapsed time: 0.109s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (2 packages loaded, 0 targets configured)
ERROR: Build failed. Not running target

Type of change

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

• Unit Tests
• Manual Tests

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules