Now that isValid() is on demand, and actionStatus is correct, we don't
need to query every possible action.
We will call setupAction which will query the state of this action when
the action is constructed. This will in turn tell us if it is valid
using the existing AuthStatus value.
This means we have all the information available without having to fetch
a whole list, simplifying the code, getting rid of a pseudo-blocking
large DBus call and an event loop all at once.
This mostly completes T12643 within KF5 with no behavioural changes for clients.