Strip out kubectl commands from journey tests

[cmwylie19]

Describe what should be investigated or refactored

There are several instances that we are using kubectl instead of the native KFC commands to interact with kubernetes resources in the journey tests. This is tech debt since KFC is the native way we interact with K8s in Pepr and KFC has come a long way since the first journey tests were written

Links to any relevant code

journey/pepr-deploy.ts

Additional context

Add any other context or screenshots about the technical debt here.

[cmwylie19]

In further review, it does not make sense to strip these out IMO.

Kubernetes-fluent-client needs a kind in which to apply, in some cases that use kubectl we are applying files with several types. Due to this, we would not be able to remove kubectl as a dependency.

[cmwylie19]

The path forward would be to parse the generated files and interpret the kinds and use KFC apply when the kinds are interpreted