UX improvements

* new project button is green
* show no-ssh error message
* fix avatar align

See merge request !1431

Documentation on how to copy your ssh key to clipboard with the console

This MR just adds some documentation in case people want to use the bash to copy their public ssh key to the clipboard.

See merge request !311

Password reset timeout

/cc @jacobvosmaer

See merge request !1428

Workflow description

See merge request !1429

Round avatars

* Make all avatars rounded for consistency
* Introduce variable for border-radius for avatars

See merge request !1427

Allow user to use http in ouath

See merge request !1426

Faster autocomplete for users/issues/emojiis

Instead of loading all issues and merge requests we load only open one.
This will reduce time load for autocomplete resources significantly

See merge request !1425

Optimize images 24.5% with ImageOptim.

Instead of loading all issues and merge requests we load only open one.
This will reduce time load for autocomplete resources significantly

Disable turbolink on links pointing out to CI services

### What does this MR do?

This MR adds 'data-no-turbolink' attribute into all links pointing to CI services.

### Are there points in the code the reviewer needs to double check?

No

### Why was this MR needed?

In rare cases where gitlab and CI service is installed on the same host, turbolink will be used for links between those two. This may result in corrupted css and javascript.

This change is harmless for installations that do not share the domain name for GitLab and CI system - in such case, all links modified are already pointing out outside of the domain so turbolink won't handle them.

### What are the relevant issue numbers / Feature requests?

I consider this a small fix, no issue has been added.

See merge request !305

API: Implement edit via API for projects

I've picked up https://github.com/gitlabhq/gitlabhq/pull/8055 fixed the few hound warnings and replaced all double quotes in the spec file where possible.

# From the original PR:

Implements edit via API for projects. Edit was part of missing features in feature request Full CRUD operations via API for projects.
http://feedback.gitlab.com/forums/176466-general/suggestions/3904506-full-crud-operations-via-api-for-projects

Feature is implemented using existing UpdateService for projects. Permission to change visibility level and name are checked in addition to check for permission to administer project.

Doesn't allow updating project namespace id, because there was existing API-method for transferring project to a group.

Documentation added to doc/api/projects.md. Uses API request PUT /projects/:id .

Tests included for:
1. Success for changing path
2. Success for changing name
3. Success for changing visibility level
4. Success for changing all other attributes
5. Success for changing name & path to existing name & path but in different namespace
6. Failure if not authenticated
7. Failure if path exists in project's namespace
8. Failure if name exists in project's namespace
9. Failure if not sufficient permission to change name
10. Failure if not sufficient permission to change visibility level
11. Failure if not sufficient permission to change other attributes

Allows updating following parameters:

* name
* path
* visibility_level
* public
* default_branch
* issues_enabled
* wiki_enabled
* snippets_enabled
* merge_requests_enabled
* description

See merge request !310

Show modal window with instructions if GitHub integration disabled

See merge request !1424

Improve commit page

See merge request !1423

API: List issues for a particular milestone

# What does this MR do?
This MR adds a new API method for retrieving the issues associated with a particular milestone. The resource is described at ":id/milestones/:milestone_id/issues", returning a simple array of issues.

I've picked up gitlab-org/gitlab-ce!113  and fixed the test for it.
From the original MR:
This feature was motivated by an in-house project for reporting--for large projects, retrieving and filtering the entire issue list by milestone was becoming too slow, particularly when pagination required multiple requests. While this resource also uses pagination, it allows the consumer to limit reporting to the particular milestone they are interested in.

@dblessing Please take a look :)

See merge request !308

Conflicts:
	CHANGELOG