MCO-293 check for correct-looking base64

The default Base64.decode method is very accepting, and will ignore
any characters not of the base64 character set, and decode those
that it does handle.  This can lead to unfortunate error messages
in the case where the message was not base64 encoded to begin with,
but a connector may be configured to expect them, so it attempts
to decode what bits it can from a message body, yeilding something
that's just the base64-decodable portions of the input string, which
will typically choke a higher level deserialiser.

Here we reject any 'base64' messages that contain characters that
aren't in the base64 character set or whitespace, in order to raise
an error sooner.
Not really.  strict_decode will reject things generated by a 1.8 Base64.encode64, so if you have mixed ruby versions you'll have the 1.8 machines generating encodings that the 1.9 nodes reject.

https://github.com/ruby/ruby/commit/2c1c462747346b05b00a0a18f28cf098526b0c1f  strict_decode64 rejects CR LF, which encode64 may add