run_command and dynamic/run_command should behave like execute as

When data pack creators and map makers use the `run_command` and `dynamic/run_command` actions in dialogs, books, etc, the goal is usually to let players execute certain preset commands without giving them full operator-permissions in multiplayer or having to enable cheats in singleplayer. However, the current behaviour of those actions makes this quite a challenge, because they behave as if the player typed the commands in Chat, rather than like `execute as`, meaning that only integer input from Dialogs can be processed for non-OP players (through /trigger), and even that is quite tedious. To address this, I propose the behaviour of those actions to change towards something resembling `execute as <player>` ran from a function. This way, creators could expose the ability to run certain privileged commands to all players, while not having to worry about the security issues arising from making them Operators.