Kubernetes Mock API

[einari]

This PR introduces a mock for "just enough" of the Kubernetes API. Meaning, for now the 2 routes we need (namespaces + pods). On the returned data, there is also just enough what we need to be able to get the initial stories completed.

How to run it

The environment is now updated to redirect '/api/v1' to the K8sMock. Restart the environment for this if already running.
The K8sMock needs to be running to be able to use this, so yarn start in the K8sMock folder.
With this, one can now go to the GraphQL endpoint and perform the Applications query and get data:

Swagger

The K8sMock service exposes a Swagger endpoint at http://localhost:3001/api/swagger/. Navigate to it and try out:

Mock Data

The data being returned sits in pods.json in the pods folder next to the PodsController in the K8sMock project and in namespaces in the namespaces folder next to the NamespacesController in the K8sMock project.

Next Steps

With the PodsController in the K8sMock already producing data, the natural next step is to use this.
I suggest creating a new object that combines the Application and its Microservices as an array on it. Something like 'ApplicationsForListing' or similar and then a query for this purpose. In the future this is what we would project to as well.

[pavsaund]

This seems straight-forward enough. Could you have a look at my comments and see if they make sense?

[einari]

The problem with the squigglies are related to this: disableSourceOfProjectReferenceRedirect- I see that this was added due to this: microsoft/TypeScript#34677.