Consider moving away from test.sh

Summary

At the moment, we use test.sh to abstract away some implementation details of the installation. It has been helpful in stages where installation was a bit complicated.

However, with &15 (closed), we have made strides to improve the installation process, and much of these implementation details are no longer required now that we generate a single manifest that can be installed with a simple kubectl apply -f manifest.yaml.

Because of this, it would be helpful to move away from test.sh because:

• It would remove a layer of abstraction
• It would reduce the number of places we need to maintain when changes are made
• It would help us (and CI) follow the end-user-documented steps for installation
• It would help us better identify ways to make installation even easier

Acceptance criteria

• Decision is made as to whether to remove test.sh
• If the decision is to remove test.sh, then an issue is created to track its removal