[wip] Add logs for kubernetes events

[sk593]

Description

Adding logs to track pod failures during schedule func test runs

Type of change

• This pull request fixes a bug in Radius and has an approved issue (issue link required).
• This pull request adds or changes features of Radius and has an approved issue (issue link required).
• This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and doesn't change the functionality of Radius (issue link optional).

Fixes: #issue_number

Auto-generated summary

🤖 Generated by Copilot at 4b779ec

Summary

🐛🚀🔧

Add error handling and debugging to functional-test workflow. Upload pod logs and events as an artifact if .github/workflows/functional-test.yaml fails.

When the test workflow fails
We don't give up or bail
We grab the logs and events
From the publish-tf-recipes step

Walkthrough

• Add an id to the recipe publishing step to enable conditional execution of subsequent steps (link)
• Add two steps to collect and upload pod logs and events as an artifact if the recipe publishing step fails (link)

[github-actions]

Test Results

2 980 tests  ±0   2 968 ✔️ ±0   2m 39s ⏱️ -11s
   256 suites ±0        12 💤 ±0 
       1 files   ±0          0 ❌ ±0 

Results for commit 4b779ec. ± Comparison against base commit 97e22b8.

This pull request removes 2 and adds 2 tests. Note that renamed tests count towards both.

github.com/radius-project/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/2491bf2d-83f6-45ca-9c69-4022c99a1c55
github.com/radius-project/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/2491bf2d-83f6-45ca-9c69-4022c99a1c55#01

github.com/radius-project/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/1e266454-e59e-4a97-a3dd-9ecffe2db377
github.com/radius-project/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/1e266454-e59e-4a97-a3dd-9ecffe2db377#01

[github-actions]

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

• Your PR branch coverage: 64.9 %
• main branch coverage: 64.9 %
• diff coverage: 0 %

The coverage result does not include the functional test coverage.

[sk593]

Moving to forks and addressing here: #6793