Surfaced while we were recording the e2e demo. I was able to navigate around this by running the console locally.

We were unable to use the operator deployed image of the crane plugin UI because the requests were returning a 400 level error while attempting to validate the credentials. This showed up pretty reliably trying to speak with a 3.11 remote cluster.

From Mike's debugging:
> It turned out that the console was acting as if we had set the authorized: true flag on the proxy config in the ConsolePlugin resource. If you set that flag it attaches the bearer token from the console UI's logged in user to any request we send to the proxy. We want it disabled so we can send our own bearer token.