feat: add auto_instrument to bootstrap

[LucasAlvesSoares]

Description

Integrates auto_instrument into bootstrap so users no longer need two separate calls to initialise the SDK.

Introduces a TelemetryConfig dataclass as the first instance of a config-object pattern that will scale to future bootstrap features (e.g. AICoreConfig). For now it exposes disable_traces and disable_batch.

Adds a new RuntimeContextSpanProcessor that reads tenant and user identity from the SDK runtime context (populated by bootstrap providers) and stamps them on every span. This prepares for a future migration where auto_instrument is removed and bootstrap becomes the sole API surface.

Renames the IAS context key TENANT_ID → APP_TENANT_ID to better reflect its source (ias.app_tid) and distinguish it from GLOBAL_TENANT_ID (ias.sap_gtid).

Before:

from sap_cloud_sdk import bootstrap
from sap_cloud_sdk.core.telemetry import auto_instrument

auto_instrument(app=app)
bootstrap(app)

After:

from sap_cloud_sdk import bootstrap

bootstrap(app)  # telemetry included

# optional tuning:
from sap_cloud_sdk import TelemetryConfig
bootstrap(app, telemetry=TelemetryConfig(disable_batch=True))

Related Issue

Closes #

Type of Change

• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Code refactoring

Breaking Changes

• TENANT_ID in sap_cloud_sdk.core.runtime_context and sap_cloud_sdk.core.runtime_context.providers is renamed to APP_TENANT_ID.

  Migration:

  # before
  from sap_cloud_sdk.core.runtime_context import TENANT_ID
  ctx.get(TENANT_ID)
  
  # after
  from sap_cloud_sdk.core.runtime_context import APP_TENANT_ID
  ctx.get(APP_TENANT_ID)

How to Test

1. Call bootstrap(app) without setting OTEL_EXPORTER_OTLP_ENDPOINT — verify a warning is logged and no error is raised.
2. Call bootstrap(app) with OTEL_TRACES_EXPORTER=console set — verify spans appear in stdout.
3. Call bootstrap(app, telemetry=TelemetryConfig(disable_traces=True)) — verify no trace initialisation occurs.
4. Call bootstrap(app, telemetry=TelemetryConfig(disable_batch=True)) — verify SimpleSpanProcessor is used (spans flush synchronously).
5. Verify existing callers of auto_instrument directly still work unchanged.
6. Make a request with an IAS JWT — verify spans have sap.tenancy.tenant_id and user.id attributes set from the runtime context.

Checklist

• I have read the Contributing Guidelines
• I have verified that my changes solve the issue
• I have added/updated automated tests to cover my changes
• All tests pass locally
• I have verified that my code follows the Code Guidelines
• I have updated documentation (if applicable)
• I have added type hints for all public APIs
• My code does not contain sensitive information (credentials, tokens, etc.)
• I have followed Conventional Commits for commit messages

Additional Notes

TelemetryConfig is intentionally minimal (disable_traces, disable_batch only). Fields like disable_metrics and middlewares are deferred to follow-up PRs. The dataclass pattern is designed to accommodate future config domains (e.g. bootstrap(app, telemetry=..., aicore=AICoreConfig(...))) without bloating the bootstrap signature.

The RuntimeContextSpanProcessor uses a lazy import of runtime_context inside on_start to avoid circular imports and to silently no-op on spans created before bootstrap runs.