Allow local authentication mode not just for development

[roee88]

Razee in local auth mode could be used by higher level controllers to manage deployments across clusters, not just for testing purposes but for regular usage as well. In this scenario the only user of Razee is a higher level K8S controller (not humans) that uses a dedicated Razee instance for managing resources (typically co-located in the same cluster).

To make this work there are several items to be addressed:

• Creation of users (graphql api) currently doesn't require authentication. This creates a security risk because the api endpoint is publicly exposed (to allow connections from the agents) - This might be considered a bug - in which repo should we open an issue?
• Document that currently there can only be one Razee instance per cluster. Basically, higher level controllers should always be configurable to use some Razee instance (dedicated with local auth or a shared instance if one already exists).
• Optionally support using the Razee Dash UI with local mode.
• Optionally allow installation with local mode
• Documents local as a legit deployment model (cf. dev only)

The alternative is to keep it as dev only and require a more complex setup for such use cases.

[roee88]

Please let me know whether this is something that you want to have or should I close the issue instead.