fix: add release name as prefix to chart resource names during deployment

[leninmehedy]

Description

This pull request changes the following:

• allow custom release name as prefix to all resources same as mirror-node resources
• update makefile scripts to use the RELEASE_NAME env var from env or .env file

Below screenshot shows an example deployment with RELEASE_NAME=fst:

Limitations:

I started working on this with the anticipation that this could allow deploying FST chart multiple times in the same namespace. For example, if a user has access to a single namespace, he/she could deploy the FST chart multiple times in the same namespace for different test scenario and avoid the explosion namespaces in the shared cluster.

However, it appears dependent charts e.g. mirror-node creates some secrets without release name prefix (e.g. it creates "mirror-passwords" instead of "{{.Release.Name}}-mirror-passwords)", so it blocks us from deploying the chart multiple times in the same namespace)

So at the end this PR doesn't add much value except the fact that it is now consistent with mirror-node resource naming. However, if mirror-node updates their secrets with release name prefix, we would be able to deploy the same chart multiple times for different test scenario and avoid the "namespace explosion" in the cluster...

Related Issues

• Closes Charts[GKE-BUG] Allow the chart to be deployed with different release-name #388

[github-actions]

Unit Test Results

  23 files  ±0    23 suites  ±0   48s ⏱️ +2s
103 tests ±0    99 ✔️ ±0  4 💤 ±0  0 ❌ ±0 
104 runs  ±0  100 ✔️ ±0  4 💤 ±0  0 ❌ ±0 

Results for commit d9009b8. ± Comparison against base commit 40e737a.

♻️ This comment has been updated with latest results.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[leninmehedy]

After discussing with Nathan we decided not to proceed in this direction because of the following reasons:

• Third-party dependent chart resources may not support multiple deployment in the same namespace (e.g. we already discovered issue with the 'secret' created by mirror-node)
• Namespace is the best and standard way to segregate test environments. So all our tests environments should be segregated using namespace to avoid confusion.

So in summary, we shall assume that the chart can be deployed only once in a namespace.

However, all FST resources should be labeled with the test related metadata (see #409)