e2e: Make order of applying / deleting templates consistent.

[v-shenoy]

Signed-off-by: Vighnesh Shenoy [email protected]

Earlier, the apply / delete functions for Kubernetes templates were using maps. Iteration order is not guaranteed for maps in Go. So, which template would get applied / deleted first would be run dependent. This matters in cases where one template is dependent on other (ex - SO depends on target deployment). This leads to noise in the KEDA pod logs with errors that are unrelated to test failures themselves.

Sorry for the large PR.

Checklist

• [x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
• [x] Tests have been added

[v-shenoy]

/run-e2e Update: You can check the progress here

[JorTurFer]

/run-e2e solace* Update: You can check the progress here

[JorTurFer]

Thanks for the improvemnt!

[v-shenoy]

/run-e2e solace* Update: You can check the progress here

[v-shenoy]

Funny, the solace test seems to run fine on my dev cluster, pastebin. @JorTurFer

[JorTurFer]

Funny, the solace test seems to run fine on my dev cluster, pastebin. @JorTurFer

could we have any dangling resource in the cluster? I'm on vacations and I don't have my computer here to connect to the cluster

[v-shenoy]

Funny, the solace test seems to run fine on my dev cluster, pastebin. @JorTurFer

could we have any dangling resource in the cluster? I'm on vacations and I don't have my computer here to connect to the cluster

I am not sure @JorTurFer

[JorTurFer]

Could you take a look please @tomkerkhove ?:pray:

[zroubalik]

/run-e2e solace* Update: You can check the progress here