V2 nonkube bootstrap must not accept a custom resource path

[fgiorgetti]

Is your feature request related to a problem? Please describe.

Today bootstrap command accepts a custom path, as an argument, for consuming input resources.

Allowing resources to be consumed from any given location, as well as from the default input/resources under the namespace home, makes it easy to use at first, but it increases complexity and makes it harder to explain and document.

When the CLI is used, resources are placed under a well known location, which is under input/resources in the namespace home.

Ideally resources should only be placed under input/resources in the desired namespace home.

This will require an extra step, to create the base directory and copy the resources, but it will make code simpler, reducing complexity and easy to explain.

Describe the solution you'd like

When bootstrapping a nonkube namespace, only read custom resources from the input/resources directory located under the desired namespace home.