feat: support global direct call validation

[adamegyed]

Motivation

While we added support for direct-call validation in #90, this was only supported for individually added selectors, because the checking type defaulted to non-global. It would be useful to have "full" support for all validation types in this path.

Solution

Check for both global and selector-based validation applicability in the direct call path.

Do this by refactoring the checking functions to take an enum with types of GLOBAL, SELECTOR, and EITHER.

Refactor the direct call tests to randomize the validation type initialization, to test both cases.

[Zer0dot]

Nice way to go about this!

Wdyt of the security implications? I think it's fine, because a nefarious module could always just request whatever function to direct-call. So, overall, I think this is a nice streamlining change!

[adamegyed]

Wdyt of the security implications? I think it's fine, because a nefarious module could always just request whatever function to direct-call. So, overall, I think this is a nice streamlining change!

Yeah, similar reasoning on my end. The status of a validation as global vs not is part of the domain it gets set up with, so if you don't want to give it global access, you just don't set that as a parameter when you install it. But in some cases, it would be nice to grant it that permission.