minimal working example on how to install Pulsar locally for development and testing

### Current behaviour

I tried to deploy Pulsar locally into Colima/K3s/Kind like Kubernetes test environment.

Firstly note a small typo in the README file; the instructions should rather be:

```console
$ helm install -n pulsar mypulsar pulsar
```

This produces the following output:

```console
NAME: mypulsar
LAST DEPLOYED: Fri Aug 1 11:40:58 2025
NAMESPACE: pulsar
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
http:///
```

The application URL is not properly filled in, and the pod is actually pending:

```console
$ kubectl -n pulsar get deployments
NAME READY UP-TO-DATE AVAILABLE AGE
mypulsar 0/1 1 0 5m38s

$ kubectl -n pulsar get pods
NAME READY STATUS RESTARTS AGE
mypulsar-768cc4dbd9-h8dlg 0/2 Pending 0 5m58s
```

This appears to be due to a failed persistent volume business:

```console
$ kubectl -n pulsar get events
LAST SEEN TYPE REASON OBJECT MESSAGE
7m27s Normal SuccessfulCreate replicaset/mypulsar-768cc4dbd9 Created pod: mypulsar-768cc4dbd9-h8dlg
7m27s Normal WaitForFirstConsumer persistentvolumeclaim/mypulsar-data-pvc waiting for first consumer to be created before binding
106s Normal ExternalProvisioning persistentvolumeclaim/mypulsar-data-pvc Waiting for a volume to be created either by the external provisioner 'rancher.io/local-path' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered.
3m42s Normal Provisioning persistentvolumeclaim/mypulsar-data-pvc External provisioner is provisioning volume for claim "pulsar/mypulsar-data-pvc"
3m42s Warning ProvisioningFailed persistentvolumeclaim/mypulsar-data-pvc failed to provision volume with StorageClass "local-path": NodePath only supports ReadWriteOnce and ReadWriteOncePod (1.22+) access modes
```

### Expected behaviour

It would be great if the default Helm chart values would work out of the box in such a way that the default deployment would lead to a locally running Pulsar test deployment.

Alternatively, if the deployment requires to customise the Pulsar configuration via Helm chart values and/or it if requires to prepare some volumes in advance, it would be great to enrich the README file in order to describe all the necessary Helm values that one should customise.

Motivation: we are looking into possibly supporting Pulsar as a compute backed in the @reanahub reusable analysis platform, for which it would be useful to have a minimal working example on how to run Pulsar locally for development and testing purposes in a K3s/Kind environment.

CC @bgruening @CameronMcClymont

Start with the README installation command and the Helm chart values used by `helm install -n pulsar mypulsar pulsar` in K3s or Kind. Reproduce the deployment with `kubectl`, inspect the pending pod and persistent-volume events, then document the required values or preparation steps so a local Pulsar test deployment reaches a running state.

Written by the indexing model from the issue text.