[appmesh-spire-server] Add support for spire-controller-manager for automatic workload registration

**Is your feature request related to a problem?**
Add support for SPIRE Controller Manager which automatically registers App Mesh SPIRE workloads. As it stands right now, workloads must be manually registered which leads to human error. The controller manager cannot be added to the cluster after-the-fact because it is required to be deployed in the same pod as the spire-server

**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
appmesh-spire-server

**Describe the solution you'd like**
Ability to configure the [spire-controller-manager](https://github.com/spiffe/spire-controller-manager) via helm. A manifest example is outlined [here](https://github.com/spiffe/spire-controller-manager/blob/main/demo/config/cluster1/spire/spire-server.yaml)

**Describe alternatives you've considered**
A description of any alternative solutions or features you've considered.

Start with the appmesh-spire-server Helm chart and compare its current deployment configuration with the linked spire-controller-manager manifest example. Determine how the controller manager should be configured through Helm and deployed in the same pod as spire-server. Done means the chart can install and configure automatic workload registration without manual registration.

Written by the indexing model from the issue text.