MultiTenancy for Kibana

Kibana as a part of ELKStack is suitable tool to display collected logs in variety of built in visualization.
However it does lack multi-tenancy layer that would help to distinguish logs of one project (tenant) from another.

Kibana in multi-tenancy would offer:
- ​project (tenant) oriented separation of the data
    * ​index patterns
    * dashboards
    * visualizations
- ​automatic index pattern creation based on project id associated with token-
preventing access to logs to non-authorized projects (tenants)
    * created ​index patterns must contain fully qualified project id (tenant id)
- storing project related/scoped settings/data (visualization, dashboards) in .kibana-{projectId} index, accessible by users having access to the given project.

Entire functionality is based on specific token property - token is one side correlated with user and on the other side with project.
Project association is used to determine what data should be visible for logged user and how to write the data back (dashboards, visualizations, etc.) to ElasticSearch on behalf of Kibana.

The implementation should be done in form of the Kibana plugin.