Allow for disabling client-side validation in V4 Post Policy

[frankyn]

When calling validateFields; it checks to make sure provided input field keys are part of a known list. This is restrictive on input and would require an update if we introduce more fields in the future (which is possible).

Follow-up:

• Does the server return a useful error?
• Is the error state opaque such that the server can't return a better error?
• If the server can be improved should we advocate that?
• If the server error can only be opaque, do we want to introduce a strict/relaxed validation option? strict: throw exception or relaxed: log a warning for customer

[frankyn]

@JesseLovelace are you still looking at this issue?

[JesseLovelace]

The server gives a 400 bad request with the following message:

<?xml version='1.0' encoding='UTF-8'?><Error><Code>InvalidPolicyDocument</Code><Message>The content of the form does not meet the conditions specified in the policy document.</Message><Details>Invalid exact match name: invalid</Details></Error>

This should be sufficient for debugging, so we'll remove the validation