Add Telemetry Integration and Enhance SDK Configuration

[armando-rodriguez-cko]

Description

This PR introduces telemetry support for tracking request performance, updates SDK configuration with enhanced flexibility, and improves test coverage to validate new and existing functionalities.

Changes Made

Telemetry Integration:

• Added request telemetry to capture:
  • Unique request IDs.
  • Latency of requests.
  • Details of the previous request (ID and duration).
• Enabled telemetry by default, with an option to disable it during SDK configuration.

Configuration Updates:

• Updated DefaultCheckoutConfiguration and AbstractCheckoutSdkBuilder:
  • Added a recordTelemetry flag to enable or disable telemetry.
  • Enhanced concurrency support for configuration creation.
• Modified ApacheHttpClientTransport to include telemetry headers in outgoing requests.

New Classes:

• Introduced RequestMetrics to store and handle telemetry data.

Testing Enhancements:

• Added CheckoutSdkTelemetryIntegrationTest:
  • Validates telemetry inclusion in headers.
  • Tests concurrent requests for telemetry uniqueness.
  • Simulates high-load scenarios to ensure telemetry integrity.
• Enhanced configuration-related tests to validate telemetry toggling and thread safety:
  • DefaultCheckoutConfigurationTest.
  • PreviousStaticKeysSdkCredentialsTest.
  • StaticKeysSdkCredentialsTest.
• Improved tests for backward compatibility:
  • WorkflowsTestIT.
  • TokensTestIT.
  • PaymentsTestIT.

Documentation Updates:

• Updated README.md to include details on telemetry and its configuration.

Impact

• Performance Monitoring: Provides valuable insights into API request performance and improves monitoring capabilities.
• Configurable Telemetry: Allows users to enable or disable telemetry as needed, offering flexibility.
• Enhanced Testing: Ensures robustness and compatibility under various scenarios, including concurrency and high-load environments.

Additional Notes

• Telemetry is enabled by default but can be disabled during SDK configuration.
• Changes are fully backward compatible.
• Introduced updates do not alter existing API behaviors.