Instance Details Redesign

Summary
=======
This is a redesign of the instance details page which will incorporate the UX collaboration done in the community before during and after the Kilo design summit. It will be based on angular and will incorporate many aspects of the development being done for the following blueprints:

https://blueprints.launchpad.net/horizon/+spec/launch-instance-redesign
https://blueprints.launchpad.net/horizon/+spec/angularize-identity-tables

Motivation
========
The instance is one of the most important interactions that users have with OpenStack. The current instance details form has been received poorly by new users and causes OpenStack to be unapproachable. We want to enable a more modern UI that is also more end-consumer friendly.

Description
=========
The instance detail panel will include a modern layout, access to enhanced descriptions, and an improved help system.

We will leverage widgets being done for identity management and launch instance to help improve consistency and reusability.

The UX mockups will provide the majority of the details.

The Instance Details screen currently includes an Actions pull-down that is a Django construct.
This feature should be implemented as a generic feature (e.g. an Angular directive) that can be used in other similar screens.

UX
===

The design is being done with the community and will be continued to be iterated on as necessary.

Wireframes, Mocks, Videos and UI Markup
---------------------------------------------------------
The user experience has been mocked up through many rounds of iteration with the community:

http://invis.io/NB1L22K4Q

The iteration in the community has led to the following concepts being incorporated:

 * Be approachable to new users with information and help readily available
 * Ease of navigation between sections of information
 * Provide quick access to advanced settings for advanced users

Testing
======
Reviewers will be able to pull the patch from Gerritt.

Outside Dependencies
==================
Is this functionality already supported in other services? Yes.

List the appropriate API calls and if they are extensions or base API functionality. The below are all the existing APIs that are base functionality which will be used. The below is the list of APIs that will likely be called, but they will only be called in a lazy loading fashion if the user accesses a tab that requires the information or performs an action the requires the API.

api.glance.image_list_detailed
api.glance.metadefs_namespace_get
api.glance.metadefs_namespace_list
api.cinder.volume_list
api.cinder.volume_snapshot_list
quotas.tenant_quota_usages
api.nova.tenant_absolute_limits
api.nova.keypair_list
api.nova.keypair_create
api.network.security_group_list
api.neutron.network_list_for_tenant
api.neutron.network_create
api.neutron.subnet_create
api.nova.server_create

Requirements Update Required
========================
None

Doc Impact
=========

Only docs that have screenshots or discussion of the current details page should be affected.