'history undo/redo/rollback' does not print superuser privileges error like 'install' does

[oturpe]

In I try to run dnf install as normal user, I get:

$ dnf upgrade
The requested operation requires superuser privileges. Please log in as a user with elevated rights, or use the "--assumeno" or "--downloadonly" options to run the command without modifying the system state.

That is fine. The same error is also printed for upgrade and remove subcommands. However, sub-subcommands of history similarly require superuser privileges, but do not have the same error. For instance:

$ dnf history undo 45
Updating and loading repositories:
Repositories loaded.
Package
Removing:
 ...
Removing unused dependencies:
 ...

Transaction Summary:
 Removing:          17 packages

After this operation, 36 MiB will be freed (install 0 B, remove 36 MiB).
Is this ok [y/N]: y
Running transaction
Failed to open lock file "/run/dnf/rpmtransaction.lock": (13) - Permission denied

Please add the warning, so it is more clear what went wrong.

[kontura]

The issue is also valid for other history commands that perform a transaction (undo,, redo and rollback).

The issue happens due to the way we determine which commands require privileges in cmd_requires_privileges().
We could either add them to the hard coded list of commands or we could add the --store argument to each one.

Personally I would prefer to add the --store argument so that dnf5 can consistently store any transaction.