SNOW-3152214: add id generator for external telemetry

[sfc-gh-yuwang]

1. Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

   Fixes SNOW-3152214

2. Fill out the following pre-review checklist:

   • I am adding a new automated test(s) to verify correctness of my new code
     • If this test skips Local Testing mode, I'm requesting review from @snowflakedb/local-testing
   • I am adding new logging messages
   • I am adding a new telemetry message
   • I am adding new credentials
   • I am adding a new dependency
   • If this is a new feature/behavior, I'm adding the Local Testing parity changes.
   • I acknowledge that I have ensured my changes to be thread-safe. Follow the link for more information: Thread-safe Developer Guidelines
   • If adding any arguments to public Snowpark APIs or creating new public Snowpark APIs, I acknowledge that I have ensured my changes include AST support. Follow the link for more information: AST Support Guidelines

3. Please describe how your code solves the related issue.

   This PR is meant to add span id generator that is needed for snowsight UI.
   for this PR, a forked id generator is used, the reason is that:
   currently snowflake-telemetry-python is pinning opentelemetry to 1.26.0, which is built with a very old protobuf version, while snowpark require using a newer protobuf version, which leads to conflicts.

We will switch to snowflake-telemetry-python implementation once they release a newer version

[sfc-gh-vguttha]

do we need this because if this is else we will not hit bit below where we are using ForkedSnowflakeTraceIdGenerator right?

[sfc-gh-yuwang]

yes, otherwise there would be compilation error

[sfc-gh-vguttha]

Can we also check first 4Bytes is timestamp in minute?

[sfc-gh-yuwang]

sure, will do