When fetching available shortcuts for a user, also permissions
are checked by the ShortcutRepository. However previously a lot
of use-cases were missed and the implemented checks were more
or less faulty, especially when it comes to non-admin users.
Therefore, three main topics are now handled properly:
* Evaluation of record edit permissions for shortcuts,
targeting the record_edit route
* Evaluation of page access permissions for every shortcut
not targeting the file list
* Proper distinction between shortcuts for file list and
the ones for other modules, since both use the "id"
argument, while for the file list, this is a string
(combined identifier), and for the rest, this is an
integer (the requested page id or the records' pid)