Remove obsolete os packaging tests

[imdhemy]

Description

• Remove the obsolete qa/os packaging tests and related configuration.
• Remove the unused distro-test and Vagrant build tooling.

Related Issues

Resolves #22870

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

PR Reviewer Guide 🔍

(Review updated until commit 48ed61a)

Here are some key observations to aid the review process:

🧪 No relevant tests

🔒 No security concerns identified

✅ No TODO sections

🔀 No multiple PR themes

⚡ No major issues detected

[andrross]

Thanks @imdhemy! Looks like you exposed a bug in our CI workflow that doesn't consider a deleted file as a change. I've got a fix here: #22881 Once that is merged we can rebase this once and ensure the gradle check workflow runs.

[msfroh]

Hey, @imdhemy, it looks like since #22719 made changes to a couple of the build.gradle files that you deleted. Unfortunately, GitHub doesn't let me resolve the conflict (by deleting the files) through the UI.

Can you please resolve the conflict from your end and push the updated commit? I've merged @andrross's fix to the change detection logic.

[github-actions]

Persistent review updated to latest commit 9b13792

[imdhemy]

@msfroh I've rebased the branch & resolved the conflicts.

[github-actions]

❌ Gradle check result for 9b13792: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 9b13792: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

Persistent review updated to latest commit d98d94b

[github-actions]

Persistent review updated to latest commit 97c0b49

[github-actions]

❌ Gradle check result for 97c0b49: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 97c0b49: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

Persistent review updated to latest commit 762b153

[github-actions]

❌ Gradle check result for 762b153: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[msfroh]

Hmm... the build failure is related to a failure on the 2.19 branch to download the Java formatter config, but AFAIK, @peterzhuamazon fixed that in #22793.

@peterzhuamazon -- do you have any idea why your fix isn't helping here? It looks like it should be fine from what I can see.

[andrross]

Hmm... the build failure is related to a failure on the 2.19 branch to download the Java formatter config, but AFAIK,

@msfroh That spotless backport on 2.19 should (might?) fix this...

[github-actions]

Persistent review updated to latest commit 0bc66ae

[github-actions]

❌ Gradle check result for 0bc66ae: null

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

Persistent review updated to latest commit 48ed61a

[github-actions]

❌ Gradle check result for 48ed61a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?