[Proposal] Add query for default methods screen

[tabuna]

Is your feature request related to a problem? Please describe.
When I work with a screen, it is often necessary to change the name, description, and actions depending on the state of the object. This usually means some override directly in the query method.

For example:

public function query(Model $model): array
{
    if ($model->exists) {
        $this->name = 'Edit post';
    }
     // ...
}

This is not what I would like to see in a method that is responsible for transferring data.
Also, this can introduce some confusion to users, for example, in issue #1277

Describe the solution you'd like

Perhaps it is worth expanding the number of methods that would receive a ready-made data set:

/**
 * Display header name.
 *
 * @param Repository $repository
 *
 * @return string|null
 */
public function name(Repository $repository):?string
{
    // return ...
}

/**
 * Display header description.
 *
 * @param Repository $repository
 *
 * @return string|null
 */
public function description(Repository $repository): ?string
{
    // return ...
}

/**
 * Button commands.
 *
 * @param Repository $repository
 *
 * @return Action[]
 */
public function commandBar(Repository $repository): array
{
    // return ...
}

Then there will be fewer actions to be performed in query and do not need to enter class properties. This approach's critical disadvantage is that because the class argument can store any variables, there will be no auto-hints in the IDE.

Additional context

Most likely, this can be done without breaking backward compatibility. Provided, of course, that the user no longer has methods named the same. There is also only one property, $permission, that should be changed into a method without actually getting and executing the query method.