Support contains/regex rules in execpolicy

It looks like prefix_rule only matches the beginning of the submitted argv. That works for direct commands, but misses cases where the sensitive command is embedded inside a shell string, e.g. bash -c "... some-command ...".

Could execpolicy support a simple contains_rule or regex_rule over the full submitted command/argv?

I know this would not be a perfect security boundary and would not replace sandboxing or runtime interception, but it would catch many practical cases without forcing users to prompt on every bash -c.