Expose websocket through helm chart

**Describe the bug**
A clear and concise description of what the bug is.

We want to use the websocket interface(https://pulsar.apache.org/docs/en/client-libraries-websocket/) supported by Pulsar. But I did not find a way to enable the websocket and expose it through ingress.

I can find another helm chart that supports to config websocket. e.g. https://github.com/kafkaesque-io/pulsar-helm-chart/blob/40267fbad7c91abe0a4b571d399a8bc97ddb58e0/helm-chart-sources/pulsar/values.yaml#L1392 and https://github.com/streamnative/charts/blob/master/charts/pulsar/values.yaml#L1139

It will be great if it can be supported in this helm chart.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

There is a way to enable and expose websocket interface using the helm chart.

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

**Desktop (please complete the following information):**
- OS: [e.g. iOS]

**Additional context**
Add any other context about the problem here.

Inspect the Helm chart's values and ingress configuration, then compare the websocket settings in the cited pulsar-helm-chart and StreamNative values.yaml files. Done means the chart provides a way to enable the Pulsar websocket interface and expose it through ingress.

Written by the indexing model from the issue text.