* Bump version to 2.0.3

* Bump version to 2.0.3

* Update Chart.yaml

* Detect insecure login and update documentation

* Regenerate translation files

* Fix travis

* Prepare for v2.0.0 release

* Fix logs breadcrumb

* Fix tooltip text formatting for workload statuses

* Add lock to settings load to avoid concurrent change
Co-authored-by: NSebastian Florek <sebastian.florek@loodse.com>

* Bump version to v2.0.0-rc3

* Fix imports

Added PowerShell equivalent so it's clear for Windows how to create the sample user.

Clarified the statement to running the snippets. When I first read the statement, and tried it out, I was confused why it wasn't working. Turns out it's because I copied BOTH snippets to a single yaml file and running that...
You have to copy it to separate yaml files and executing them separately to work.

The documentation is out of date. It suggests that certificates will be automatically picked up by the dashboard container, if they are named `dashboard.crt` and `dashboard.key`. This has caused a lot of confusion and multiple issues have been opened about this issue. 

https://github.com/kubernetes/dashboard/issues/2995
https://github.com/kubernetes/dashboard/issues/2751

I have provided instructions for editing deployment to add ` --tls-cert-file` and `--tls-key-file` arguments
I have renamed certificated to the defaults used by certmanger, as that's what most people will end up using. 
Please provide feedback if you are unhappy with this PR, but this needs to be corrected.

openssl requires over 4 characters for password.

Also `Creating sample user`.

Migrate Wiki pages for Installation and Certificate Management into `docs`.

* Added user impersonation and username to ui

* groups working

* Added unit tests, extras for impersonation

* added docs

* fixed formatting to be consistent

* updates per pr review

* ran npm frontend:fix per travis ci

* Add architecture doc
Move images to the new dir

* Add deps managment doc

* Update some of the docs

* Update link to the docs

* Add links to the wiki

* Update 1.6.x-and-below.md

* Update 1.7.x-and-above.md

* Update architecture.md

To migrate wiki contents into `docs/`, prepare directory and file structures.
Contents of each pages would be added as latest in subsequent PRs.