ci: schedule long-running OTel conformance tests

[zhongkechen]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Issue Link, if available

aws/aws-durable-execution-conformance-tests#90

Description

Restore the daily 07:00 UTC trigger from the former shared Java OpenTelemetry workflow. Scheduled runs reach the reusable orchestrator with a schedule event, which automatically checks the active day-scale run or launches the next one.

Related PRs:

• ci: schedule long-running OTel conformance tests aws-durable-execution-sdk-js#843
• ci: schedule long-running OTel conformance tests aws-durable-execution-sdk-python#665

Demo/Screenshots

N/A

Checklist

• I have filled out every section of the PR template
• I have thoroughly tested this change

Testing

Unit Tests

N/A; this is a workflow-trigger-only change.

Integration Tests

• Parsed .github/workflows/otel-conformance-tests.yml successfully with Ruby YAML
• git diff --check

Examples

N/A

[github-actions]

Codex AI review

No actionable findings. Residual risk: the daily launch/check path depends on the externally pinned reusable workflow and is only exercised after merge on the default branch.

Reviewed commit a3909853fed2a958386be0ec6eaae6d354e6f655. Workflow run

[github-actions]

Claude AI review

No actionable findings.

This PR is a scoped, CI-trigger-only change to .github/workflows/otel-conformance-tests.yml:

• Adds a daily schedule trigger (0 7 * * *, 07:00 UTC).
• Bumps the pinned conformance-repo SHA from 0f0b5bda… to 91740c98… consistently in both the reusable-workflow uses: ref (line 61) and the conformance_test_ref default (line 68).

Verified: valid cron syntax and correct YAML placement of schedule under on:; both SHA references updated consistently with no stale 0f0b5bda… occurrences elsewhere; and the input-fallback expressions (sdk_ref, conformance_test_ref, phase) resolve safely for a schedule event where github.event.pull_request is absent. There are no Java, serialization, or checkpoint/replay changes, so the SDK-specific review dimensions don't apply, and the lack of unit/integration tests is appropriate for a workflow-trigger change.

Residual risk: For scheduled runs, phase still defaults to 'short' (line 105) because inputs.phase is empty on a schedule event. The intended "check the active long run or launch the next one" behavior therefore depends entirely on the external opentelemetry-orchestrator.yml special-casing github.event_name == schedule rather than honoring the phase input. That orchestrator lives in another repository and cannot be verified from this diff — worth confirming against the pinned orchestrator SHA that schedule events bypass the phase value.

Reviewed commit a3909853fed2a958386be0ec6eaae6d354e6f655. Workflow run