Make sure resource names are URI-escaped

[heaths]

Partly fixes #15784

[heaths]

Even if I escape the path segments including the certificate, key, or secret name,

1. ":" is a valid path character but still gets rejected (HTML error response).
2. ":" query string-escaped as "%3a" still gets rejected (HTML error response).

The " " (space) in a name still seems to work based on testing, as does "(" and ")". This seems to be a problem with the service, so I don't think the code changes here are necessary.

[jsquire]

Hi @heaths. There hasn't been recent engagement on this PR. Would you please be so kind as to let us know if this is still an active work stream or if the PR should be closed out?

[heaths]

I'm following up here: #15784 (comment)

[heaths]

Closing as the service cannot address the bug at this time, and - while the error message is not helpful - the behavior with getting a RequestFailedException is correct and we don't want to overzealously pin to a current behavior that may cause compatibility issues in the future.