Utilize .Release.Name as Standard Prefix for All Kubernetes Resources in Helm Chart

[thoma01]

Is your feature request related to a problem? Please describe.
Currently, when deploying Fission using Helm, the .Release.Name is not consistently used as a prefix for all Kubernetes resources. This can be problematic when trying to maintain multiple Fission installations within the same namespace or cluster, as it could lead to naming conflicts or make it difficult to distinguish resources belonging to different Fission installations. It is frustrating because it limits the ability to have fine-grained control over the deployment and can complicate the management of resources within the cluster.

Describe the solution you'd like
I would like the Fission Helm chart to be updated so that .Release.Name is used as a standard prefix for all Kubernetes resources created by the chart. This includes but is not limited to pods, services, deployments, and any other resource that is part of the Fission installation. The Helm chart should utilize the fullname helper template that is already present to ensure consistency across resource names and to adhere to Helm chart best practices.

Describe alternatives you've considered
An alternative solution could be to provide a chart value that allows users to specify a custom prefix for resource names. This value would then be used throughout the Helm chart templates to prefix the names of all Kubernetes resources. While this approach offers more customization, it may introduce additional complexity to the chart.

Another alternative is to manually edit the resource names post-deployment with scripts, but this is not ideal as it can cause disruptions and does not play well with the declarative nature of Helm and Kubernetes.

Additional context
Using the .Release.Name as a prefix is a common pattern in Helm charts and is recommended for better resource management and clarity. It is especially important in environments where multiple instances of the same application need to coexist without conflict. Adopting this pattern would enhance the usability of the Fission Helm chart and align it with community standards.