Container names are hard to distinguish

**Is your feature request related to a problem? Please describe.**
The names of the containers "manager" and "pre-delete-controller-cleanup" that gets created by the deployment makes it hard to distinguish that it is a part of vault secrets operator.

There are multiple ways to distinguish that the container is part of the vault-secrets-operator deployment, but if you're looking at a list of container names or filtering data by container name it gets hard to distinguish.

**Describe the solution you'd like**
The name of the containers should be related to the product. Maybe prefixed with "vso-" or just rename the manager container to "vault-secrets-operator".

**Describe alternatives you've considered**
N/A

**Additional context**
I checked a couple of some unrelated applications helm charts. The convention seems to be that the container name just follows the chart name, or application name.

Locate the deployment and Helm chart templates that create the manager and pre-delete-controller-cleanup containers. Review how their names are assembled and compare the requested product-related naming options. Done means both container names clearly identify Vault Secrets Operator without breaking the deployment.

Written by the indexing model from the issue text.