Unselect all other roles when selecting “No one”

Update tests and handle “No one” role option

Fix "Projected" to "Protected" misspelling

1. Builds on dd26f4e7fa418df7baeb8de057b28554c29ea826

(Protected branch access levels)

1. Add a `autocomplete/project_groups` controller action. Prefer this to
   `autocomplete/groups` because the latter (wierdly) seems to break
   other dropdowns that list groups.

2. This commit does _not_ change the actual UI, because this is probably
   better saved for @alfredo1 to work on. However, all the other pieces
   have been set up, so there shouldn't be a need for any more backend
   changes.

1. A protected branch access level `belongs_to` a group in addition to a
   user. When access for a user is checked, see if the user is present
   in the access level's group, if any.

2. If a group is added to a project with `:reporter` access or lower,
   adding a group to a proteted branch does _not_ grant access, since
   the `push_code` ability is still checked. This is tested with a few
   hundred new tests in `git_access_spec`.

[ci skip]
Signed-off-by: Rémy Coutable <remy@rymai.me>

Add user last activity info

Adds `last_activity_at` info to users to track any activity from the user including any Git operations or logging in into the UI.

This adds a table with a 1-1 relationship with users, that gets updated every time the user logs in or runs any Git operation.

<br />
**Things to check:**

` Projects::GitHttpController` reads:

```ruby
# This file should be identical in GitLab Community Edition and Enterprise Edition
```

with no explanation. With this change, they will diverge as I added a `log_user_activity` method there. Not sure if this is a problem...

<br />

This MR allow us to query the DB for user activity, as requested by https://gitlab.com/gitlab-org/gitlab-ee/issues/1022

### mySQL examples - active users last month:

```sql
SELECT u.username,
       a.last_activity_at
FROM   users u
       INNER JOIN user_activities a
               ON u.id = a.user_id
WHERE  last_activity_at > (SELECT Now() - INTERVAL 1 month) -- INTERVAL '1 MONTH' in postgreSQL
ORDER  BY last_activity_at; 
```

```sql
SELECT Count(*)
FROM   user_activities
WHERE  last_activity_at > (SELECT Now() - INTERVAL 1 month); -- INTERVAL '1 MONTH' in postgreSQL
```

Fixes https://gitlab.com/gitlab-org/gitlab-ee/issues/1022

See merge request !781

User groups (that can be assigned as approvers)

Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/180

See merge request !743

It uses a user activity table instead of a column in users.
Tested with mySQL and postgreSQL

Convert CHANGELOG-EE to Markdown

All this does is convert the version sections into headers. The list
items shouldn't really be indented by two spaces, but it makes no
difference to the rendering and this way we retain authorship history
for the actual changes.

[ci skip]

Related to https://gitlab.com/gitlab-org/release-tools/merge_requests/29

See merge request !804

All this does is convert the version sections into headers. The list
items shouldn't really be indented by two spaces, but it makes no
difference to the rendering and this way we retain authorship history
for the actual changes.

[ci skip]

Related to https://gitlab.com/gitlab-org/release-tools/merge_requests/29

Remove ashley since she no longer works here

I'll send another MR to the handbook to add a step to offboarding so we don't miss these in the future.

Which would have been appropriate labels for this?

See merge request !803

Decrease maximum time to wait for a mirror process to finish from 1 day to 2 hours

This MR proposes to decrease the time that GitLab waits before to mark a mirror update process stuck as `failed`.  
Full description of the scenario in #1093  
Now this time is one day. When the problem happens, the user sees during one day that the project was updating from upstream.  
If a project has been updating from a remote for longer than 2 hours, we could conclude that something went wrong, mark the mirror as `failed` and retry next time.

Closes #1093

See merge request !791

Reset Jenkins password if username was left blank

So we not only reset password if URL was changed, but also for username. Also, still require username if a new password was set.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/22430

See merge request !775

CE to EE following update of `db/schema.rb` with `activerecord_sane_schema_dumper`

Resolved conflicts:

```
UU app/controllers/projects/merge_requests_controller.rb
UU app/helpers/merge_requests_helper.rb
UU app/views/projects/merge_requests/widget/_open.html.haml
UU db/schema.rb
UU doc/README.md
UU spec/lib/extracts_path_spec.rb
UU spec/services/merge_requests/refresh_service_spec.rb
```

See merge request !800

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Fix Git access panel for Wikis when Kerberos authentication is enabled

When Kerberos authentication is enabled, the `Git Access` panel for project's Wiki return a 500 Error. Details in #1109   
The MR provides the missing code to generate the Kerberos URL for Wiki projects.  
Closes #1109

See merge request !795

Added documentation chapter for Git attributes

See https://gitlab.com/gitlab-org/gitlab_git/issues/28 for more information.

See merge request !6826

Use activerecord_sane_schema_dumper

## What does this MR do?

EE side of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6827.

> `ActiveRecord::SaneSchemaDumper` modifies the behavior of Rails’ `ActiveRecord::SchemaDumper` so that the generated `db/schema.rb` file doesn’t contain any useless/harmful whitespace column alignment.

## Why was this MR needed?

To reduce potential conflicts in `db/schema.rb` (see https://gitlab.com/gitlab-org/gitlab-ee/issues/715).

See merge request !799

Use activerecord_sane_schema_dumper

## What does this MR do?

> `ActiveRecord::SaneSchemaDumper` modifies the behavior of Rails’ `ActiveRecord::SchemaDumper` so that the generated `db/schema.rb` file doesn’t contain any useless/harmful whitespace column alignment.

## Why was this MR needed?

To reduce potential conflicts in `db/schema.rb` (see https://gitlab.com/gitlab-org/gitlab-ee/issues/715).

See merge request !6827