We have a BitBucket connector that is using token authentication. When we needed to renew the token the new value included a forward-slash. That value was entered into the Secret value but it caused errors throughout the pipeline as the forward-slash is not url encoded. How does Harness handle this situation? Since we may / may not know what the secret value is, does it handle managing encoding of special characters separately? How would this be handled on automatically generated tokens where we don't necessarily know the value or what's included in it?