modules: Add module info command

[pkratoch]

No description provided.

[jan-kolarik]

It would be great to enable (at least some of) the existing tests for module info and module list in our CI. Currently, the background for tests relies on the module install command, but this shouldn't be mandatory for all tests. I believe we can address this by preparing the phase with the dnf4 command. But I've also noticed the functionality for listing installed modules is missing, so perhaps we can just create a follow-up ticket for the tests to ensure it's not overlooked in the future?

[jan-kolarik]

LGTM

[j-mracek]

May I ask you to provide CI tests for the command? It is not a blocker for PR, but I recommend to have an external tracker.

[pkratoch]

Yes, I plan to enable the CI tests that use info and not install or other unimplemented commands (though these tests mostly test something else and just happen to use info) and I will create an issue for those that use the install command.

But I could also create at least one test specifically for info that doesn't use install until the install command is implemented, if you think it would be better...

[jan-kolarik]

Yes, I plan to enable the CI tests that use info and not install or other unimplemented commands (though these tests mostly test something else and just happen to use info) and I will create an issue for those that use the install command.

But I could also create at least one test specifically for info that doesn't use install until the install command is implemented, if you think it would be better...

The issue is fine for now I'd say. And related to the missing install command, I believe we can resolve it by utilizing the Given I set dnf command to ... construct in the tests. This way, we can set up the preparation phase using dnf4 and then use dnf5 to test the info or list output. I've tested it briefly locally, and I can prepare a PR later against the issue you'll create.