Pulsar Manager Persistence in HerdDB

**Is your feature request related to a problem? Please describe.**
Currently the Pulsar Manager is not persisted outside of the container it is running in.
This means reconditioning of it is necessary should the helm chart be reinstalled. This is not a favorable solution.

**Describe the solution you'd like**
We can either provide a custom jdbc connectionstring to an external storage medium or use the zookeeper to store this data.
I think storing in the zookeeper should be the preferred solution.
The default value in `values.yaml` for the key: `pulsar_manager.configData.URL` (as well as others that need tuning) should be set according to: https://github.com/apache/pulsar-manager#default-test-database-herddb

**Describe alternatives you've considered**
External DB: keeping data in Zookeeper puts Zookeeper as a central point of data and should therefore be favored.

Start with values.yaml and the Pulsar Manager documentation linked in the issue, focusing on pulsar_manager.configData.URL and the other values that need tuning. Determine whether the chart should configure HerdDB through ZooKeeper or an external JDBC connection, then verify that Pulsar Manager data survives a Helm chart reinstall.

Written by the indexing model from the issue text.