Separate dashboard into it's own deployment and add persistence

[FleetAdmiralButter]

Hi,

This is still a work in progress and requires some testing, but I've done some work around fixing #55 so that the dashboard is able to persist changes.

I've also split the dashboard out into a separate deployment so the the LAPI can be run in a high-availability configuration without also having multiple instances of the dashboard running (which consumes significant memory).

Here's a summary of the changes I've made:

1. Split the dashboard into a separate deployment manifest with it's own service and ingress.
2. Added persistent volume configuration for the dashboard.
3. Modified the initContainer command for the dashboard so that it does not overwrite the user's existing database.
4. Updated values.yaml accordingly with a dedicated section for the dashboard. By default, I've set a podAffinity so that the dashboard is scheduled onto the same node as the LAPI so that this still works if the user only has access to ReadWriteOnce storage classes.
5. Added a replicas field for the LAPI deployment to allow for it to be deployed in a high-availability configuration.

It would be great if I could get some feedback around the direction I'm taking this in. We're using this fork of the Helm chart internally to run a HA CrowdSec LAPI and would like to contribute these changes back.

[he2ss]

@FleetAdmiralButter,

Did you get any chance to take a look again on this PR.
Do you still want to handle this ?