Allow filtering containers by command

[arsenalzp]

This PR is intended to implement feature requested in issue #24664

I decided to implement filtering of commands to all kind of containers: for external and for managed by podman, I guess, this approach is better than just implementing this feature for a single sort of container.

If you don't want to accept this approach then I will put it away and implement filtering for external container only.

Does this PR introduce a user-facing change?

None

[giuseppe]

the change LGTM, but you'll need to update the man pages too

[arsenalzp]

the change LGTM, but you'll need to update the man pages too

Thank you!
All related man pages have been updated, however I have the following issue on the validation stage:

hack/xref-helpmsgs-manpages
xref-helpmsgs-manpages: 'podman container list --format ' lists '.Commands', which is not in docs/source/markdown/podman-ps.1.md
xref-helpmsgs-manpages: 'podman container ps --format ' lists '.Commands', which is not in docs/source/markdown/podman-ps.1.md
xref-helpmsgs-manpages: 'podman ps --format ' lists '.Commands', which is not in docs/source/markdown/podman-ps.1.md
make[1]: *** [Makefile:608: xref-helpmsgs-manpages] Error 1

Could you please me an advice how to fix it?

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: arsenalzp
Once this PR has been reviewed and has the lgtm label, please assign vrothberg for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[arsenalzp]

All objections were removed, all applicable filters were applied for external containers with corresponding tests.

[rhatdan]

Looks like you did not update man pages correctly.

[Luap99]

This isn't really what I had in mind since it still duplicates all the filtering functions.

My idea was to define a interface for the filter function type
func(container *libpod.Container) bool, i.e. instead of using the Container struct it just accept and interface the implements all the access methods And then we just have to do that for the external container and Container struct.

That way there is no need to duplicate the GenerateFilterFunc... funxtions

[arsenalzp]

Looks like you did not update man pages correctly.

Hello,
I'll work on it once back from vacation.

[arsenalzp]

This isn't really what I had in mind since it still duplicates all the filtering functions.

My idea was to define a interface for the filter function type func(container *libpod.Container) bool, i.e. instead of using the Container struct it just accept and interface the implements all the access methods And then we just have to do that for the external container and Container struct.

That way there is no need to duplicate the GenerateFilterFunc... funxtions

Hello,

I absolutely agree with you! However, that improvement might be implemented in separate PR due to its complexity as it affects not only main code but tests as well, I'm ready to support/work on it.

It is more wise in this PR accept changes which affect filtering feature only.