[New Feature]: Make non-mods able to use "@wingetbot run" as well.

### Description of the new feature/enhancement

Considering how massive the problem with `Installer-Error-Dynamic-Scan` has got by now (See https://github.com/microsoft/winget-pkgs/pulls?q=is%3Apr+is%3Aopen+label%3AInternal-Error-Dynamic-Scan and #317960), making non-mods able to run `@wingetbot run` without the bot claiming non-mods don't have sufficient permissions, would've been one of several ways to alleviate the problem slightly.

### Proposed technical implementation details (optional)

Make it so that Wingetbot no longer requires any permissions in order to use `@wingetbot run`.

The issue identifies the @wingetbot run command and its permission check but names no files or tests. Start by locating the command’s authorization handling and checking how moderator and non-moderator requests are distinguished. Done means non-moderators can invoke the command without an insufficient-permissions rejection, with coverage for both roles.

Written by the indexing model from the issue text.