When a user is not logged in, we want to show the `New Issue` link so
he gets directed to the login flow first.

When a project is archived, we never want to show the link.

This prevents performing the requests, and disables all emoji reaction buttons

This could only be possible for users that can create merge requests
within a project.

So they need to be a allowed to create a branch and create a merge request.

When a project is archived, don't show the button on the index page
of merge requests

So we can distinguish between the permissions on the source and the
target project.

- `create_merge_request_from` indicates a user can create a merge
  request with the project as a source_project
- `create_merge_request_in` indicates a user can create a merge
  request with the project as a target_project

Rename delete_protected_branch ability to push_to_delete_protected_branch to prevent confusion with destroy_protected_branch

The TIMESTAMP data type is used for values that contain both date and
time parts. TIMESTAMP has a range of '1970-01-01 00:00:01' UTC to
'2038-01-19 03:14:07' UTC.

A Forever lib class was included to handle future dates for PostgreSQL
and MySQL, also changes were made to DeployToken to enforce Forever.date

Also removes extra conditional from JwtController

- Adds a default on expires_at datetime
- Modifies deploy tokens views to handle default expires at value
- Use datetime_with_timezone where possible
- Remove unused scopes

Also, fixes broken specs

Kamil Trzcińśki authored 6 years ago and Mayra Cabrera committed 6 years ago

We use controller actions to pass a newly created token and errors

Also:
- Changes scopes from serializer to use boolean columns
- Fixes broken specs

Also fixes spec failures on presenter and docs

- Keep 'Deploy Section' open upon save, otherwise the token might get
  lost
- When an error appears, display the error inside the form and also keep
  the Deploy Section open
- Changue copy of revoke modal

Includes:
- Model, factories, create service and controller actions
- As usual, includes specs for everything
- Builds UI (copy from PAT)
- Add revoke action

Closes #31591

Repository archives are always named `<project>-<ref>-<sha>` even if
the ref is a commit. A consequence of always including the sha even
for tags is that packaging a release is more difficult because both
the ref and sha must be known by the packager.

- add `<project>/-/archive/<ref>/<filename>.<format>` route using the
`-` separator to prevent namespace collisions. If the filename is
`<project>-<ref>` or the ref is a sha, the sha will be omitted,
otherwise the default filename will be used.
- deprecate previous archive route `repository/<ref>/archive`

The LFS files will be included in the `lfs-objects` directory in the archive.

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>