TCP Query/Response fields are not encoded properly

[adriansr]

What happened:

The query and response values are internally encoded in base64 only when they don't look like base64 data already.

This causes single words composed of alphanumeric characters to be sent to the API as-is, and later they are decoded as base64, resulting in bogus data displayed in the UI and possibly the check failing in the SM agent.

What you expected to happen:

These configuration fields are always encoded as base64.