Move debug.sh & timeout.sh to a proper e2e

[soltysh]

In comparison with the original I:

• fixed the messages checked in debug.sh which somehow were completely wrong 🙀
• fixed the messages which were responsible for many timeout.sh failures
• removed some duplicate tests for --keep-readiness and --keep-liveness b/c they were checking empty string

/assign @sallyom

[soltysh]

/retest

[sallyom]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sallyom, soltysh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• test/extended/OWNERS [soltysh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hardys]

/cherry-pick release-4.9

[hardys]

Looks like backporting this will solve https://bugzilla.redhat.com/show_bug.cgi?id=1998963

[openshift-cherrypick-robot]

@hardys: #25638 failed to apply on top of branch "release-4.9":

Applying: Squash methods into a single used one
Using index info to reconstruct a base tree...
M	test/extended/util/framework.go
Falling back to patching base and 3-way merge...
Auto-merging test/extended/util/framework.go
No changes -- Patch already applied.
Applying: Move timeout.sh to a proper e2e
Using index info to reconstruct a base tree...
A	test/extended/testdata/cmd/test/cmd/timeout.sh
Falling back to patching base and 3-way merge...
CONFLICT (add/add): Merge conflict in test/extended/cli/timeout.go
Auto-merging test/extended/cli/timeout.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 Move timeout.sh to a proper e2e
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[soltysh]

@hardys you'll likely need to pick manually what you care about since that's one of many PRs rewriting the tests, so it might not be that simple to backport 😞

[hardys]

Thanks @soltysh - I was mistaken anyway - the change I need was in #26415 where the hard-coded busybox image was removed on master, but we're now seeing failures in 4.9 jobs due to the check for only known images