refactor(e2e): deduplicate DescribeTable bodies across tools

[IrvingMg]

Description

As discussed in #527 (review), this cleanup commonizes the e2e tests logic.

Related issues

Since this is the last PR for the migration of e2e tests to Ginkgo

• Closes Migrate E2E tests to Ginkgo framework #381

How was this tested?

• make e2etest

LLM usage

N/A

Checklist

• I have read the contribution guide.
• The linter passes locally (make lint).
• The e2e tests of at least one tool pass locally (make test_ctr, make test_nerdctl, make test_docker, make test_crictl).
• If LLMs were used: I have read the llm policy.

[netlify]

✅ Deploy Preview for urunc canceled.

Name	Link
🔨 Latest commit	20df3a4
🔍 Latest deploy log	https://app.netlify.com/projects/urunc/deploys/69c68b5e65367500085303b4

[IrvingMg]

@cmainas Since this PR closes the Ginkgo migration issue, should I update the description to also close these two related issues?

• Improve error handling in e2e tests and get container's logs in case of failure #207
• ci: Make e2e testing more robust #200

[cmainas]

Thank you @IrvingMg for this PR.

I only have one comment for the crictl's pod creation. Other than that everything looks good.

For #200, let's keep it open because we still experience a lot of failures due to image pulling. One approach is to migrate the test images to docker (#444).

For #207, the ginkgo migration has definitely improved the error messages and we also capture the urunc debug logs. Would it be possible to also get the contianer's logs, when we have an error in starting it? If the error takes place on the create step, then there will be no logs.

[IrvingMg]

Thanks for reviewing!

For #200, let's keep it open because we still experience a lot of failures due to image pulling. One approach is to migrate the test images to docker (#444).

I see, makes sense.

For #207, the ginkgo migration has definitely improved the error messages and we also capture the urunc debug logs. Would it be possible to also get the contianer's logs, when we have an error in starting it? If the error takes place on the create step, then there will be no logs.

Sure, I’ll create a separate PR for that change and then close #207.

[cmainas]

Thank you @IrvingMg for the cleanup. It looks good.