The LimitRange object affects Squonk pods that do not set a limit

[alanbchristie]

We have recently removed the CPU resource limit on a number of Squonk Pods but the LimitRange object deployed to the namespace replaces the empty value with the limit value (i.e. 1). The limit range was put in place to provide requests and limits for nextflow cells, which occupy the same namespace as Squonk.

We probably need to execute 'nextflow' cells (where control of resources is a little more difficult) in a separate namespace where the limitrange object can be used. Namespace can be passed to Nextflow vis it's k8s executor config.

This is a potentially complex change: -

1. Squonk will need to support launching Nextflow in oterh namespaces (relatively simple)
2. The deployment will need to create a <squonk-namespace>-nextflow namespace
3. The squonk Servce account will need execution rights in the new namespace
4. The LimitRange is then applied to the nextflow namespace