Login page unresponsive if I configure the console to show both the underlying cluster and its proxy

[k-wall]

Describe the bug

I am trying to use the StreamsHub Console (0.8.5) and the Kroxylicious Proxy (0.13.0) together. I am configuring the Console to show both the underlying cluster and its proxy.

I have Strimzi, Kroxylicious Operator and Console Operators installed.

A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Kafka:

kubectl create namespace kafka
kubectl apply -f https://strimzi.io/examples/latest/kafka/kafka-single-node.yaml -n kafka 

2. Proxy

curl -v  -L https://github.com/kroxylicious/kroxylicious/releases/download/v0.13.0/kroxylicious-operator-0.13.0.zip -O
unzip kroxylicious-operator-0.13.0.zip
oc apply -f examples/simple

3. Console

oc apply -n my-proxy -f -  << EOF
apiVersion: console.streamshub.github.com/v1alpha1
kind: Console
metadata:
   name: console
spec:
  hostname: kafka-console.apps.rosa.xxxxxxx
  kafkaClusters:
    - listener: plain
      name: my-cluster
      namespace: kafka
    - name: my-proxy
      properties:
        values:
          - name: bootstrap.servers
            value: 'my-cluster-cluster-ip-bootstrap.my-proxy.svc.cluster.local:9292'
          - name: security.protocol
            value: PLAINTEXT
EOF

4. Go to the console login page
5. Login page appears showing the two clusters
6. Click either Login to Cluster button
7. Expected behaviour - browser should refresh and show the "Welcome to the streams for Apache Kafka console - click to logon anonymously" page
   Actual behaviour - nothing happens. Button seems unresponsive.

I notice if I add unique ids to the two kafkaCluster objects in the Console CR the problem disappears.

We are aware of the Kroxylicious defect that means that a proxied cluster shares the same cluster id as the cluster itself. This might be material to this defect kroxylicious/kroxylicious#379.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[MikeEdgar]

The primary problem here is that the identifier is being URL encoded by the API and the padding characters, = are not being properly handled in the front-end. I'll open a PR with a change to encode without padding to address it.