Improve Azure deployment test diagnostics

[jiaenren]

Description

The Azure deployment test could mistake a broken local kubectl port-forward for a logger failure, and teardown could remove the cluster before CI saved enough evidence.

This PR:

• retries strict log reads and restarts the port-forward once;
• classifies transport, OETF runner, and test failures separately;
• captures bounded, secret-conscious diagnostics before Terraform destroy;
• links Slack alerts to the failed step and named artifacts.

The full Azure deployment remains label-gated, so this PR does not start cloud infrastructure.

Issue - None

Validation

• bazel test --noshow_progress --test_summary=terse //test/oetf/tests/...
• focused Python lint and type checks
• actionlint with ShellCheck, bash -n, and YAML duplicate-key validation

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 0efb3ac0-a420-4a30-81c9-1d0221838a6e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}