Dynamic Validator Refactor for Operator Compatibility

[bennerv]

Things to note:

1. Removed the dependency from dynamic on any document specific types, so it should be able to be called from anywhere that matches the arguments for NewValidator.
2. OpenshiftCluster-validatedynamic still contains validation specific to the context of the RP. If some of this functionality needs to be moved elsewhere, it would [ideally] move into dynamic.go.
3. OpenshiftCluster-validatedynamic utilizes the caching mechanism of the virtualnetworkclient in some of it's vnet specific validation. This can be changed or modified to use the raw virtualNetworkClient in cache.go instead of borrowing.

Which issue this PR addresses:

Refactor openshiftcluster-dynamicvalidator into an interface that allows some functions to be used outside of the context of the RP.

What this PR does / why we need it:

This should allow us to call validation methods from the context of the operator to expose them as conditions.

Test plan for issue:

Unit tests
E2E tests

Is there any documentation that needs to be updated for this PR?

No

[mjudeikis]

I think this makes code more re-usable but it makes all the code exponentially more complicated and harder to read. Im ok with this but we just need to be more aware of things like this. Now it requires more experienced reviews, code is harder to change, any task touching this code will be much harder. Just saying :)

[mjudeikis]

vnetId

[bennerv]

Fixed

[mjudeikis]

json:"vnetId,omitempty"`

[bennerv]

Fixed

[mjudeikis]

Please raise follow-up to try to get this generalized so this would be set by called instead in the initiation