Refactor podman search to be more code friendly

[jwhonce]

• JSON and API description fields are no longer truncated. Formatting
  moved to client, better support of MVP.
• --no-trunc now defaults to true
• Updated tests for changes

Closes #11894

Signed-off-by: Jhon Honce jhonce@redhat.com

What this PR does / why we need it:

How to verify it

Which issue(s) this PR fixes:

Special notes for your reviewer:

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jwhonce

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:

• OWNERS [jwhonce]

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

[ashley-cui]

LGTM, but I think [NO NEW TESTS NEEDED] needs to be in caps

[TomSweeneyRedHat]

Changes look OK to me, but same questions here as in #11892. Do we mess up expected behavior, especially so for someone who may have built a script based on the prior return?

[vrothberg]

LGTM, but I think [NO NEW TESTS NEEDED] needs to be in caps

I actually think that the --no-trunc=true could be checked for in a test. For instance, by making sure that no cell ends with ....

[vrothberg]

Changes look OK to me, but same questions here as in #11892. Do we mess up expected behavior, especially so for someone who may have built a script based on the prior return?

We'll only find out once we ship but 4.0 is the next chance we'll have. I don't think that anyone would bark after this change here though as I find it unlikely that folks rely on things being truncated by default.

[ashley-cui]

/lgtm