fix: manage podman inspect result as a list also

[too-common-name]

What type of PR is this:

/kind bug
/area odo-on-podman

What does this PR do / why we need it:

This PR addresses an issue when using the odo commands with Podman, specifically related to the podman pod inspect command. Due to a recent change in Podman (see podman PR #21514), the output now returns a JSON array instead of a JSON object. This PR modifies odo to correctly handle this change, preventing errors in commands like odo debug and odo logs when running on Podman.

Which issue(s) this PR fixes:

Fixes #7252

PR acceptance criteria:

• Unit test

• Integration test

• Documentation

How to test changes / Special notes to the reviewer:

[openshift-ci]

Hi @too-common-name. Thanks for your PR.

I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[netlify]

✅ Deploy Preview for odo-docusaurus-preview canceled.

Name	Link
🔨 Latest commit	74f5ae4
🔍 Latest deploy log	https://app.netlify.com/sites/odo-docusaurus-preview/deploys/67095764dd2213000819a953

[rm3l]

/ok-to-test

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[rm3l]

Thanks @too-common-name !!

[too-common-name]

Thank you for merging this! This was my first contribution as a RedHatter, and I'm really excited to have been able to help improve odo. I hope this is just the first of many contributions to come. Looking forward to learning more and contributing further to the community!