This commit introduces a new Sign In / Sign Up form for trials.
It behaves almost like the original with some exceptions:
- removed ability to sign in via social networks;
- removed captcha on the sign in form;
- field 'name' replaced by two new fields 'first_name' and 'last_name';

This adds a notification to let users know of our updated privacy
policy.

Users can dismiss the notification either by following the link or
closing the notification via an "x" icon.

- Adds UI to configure in group and project settings
- Removes notification configuration for users when
disabled at group or project level

When querying a Design List Item, the event and notesCount fields
are now available at the top level

Check for project group license
If needed, check if user can upgrade group

- Default
- Unapproved

Refactor loading behavior

- Let's fetch the main chart first (instead of the MR table)
and use the responde to determine
whether the user has access to a given group

- This allows metricTypes to be shared across module
- Render "days_to_merge" metric in "Time to merge" column
- Render correct column options

- no bulk updates in the first iteration
- moving only between the same types
  (epics, epic_issues)

- Also rename EKS dropdown to cluster form dropdown

A project will no longer be created if an invalid project name is
provided. This makes it possible for the API and controllers to behave
in a consistent manner, since it's easy to make a mistake and use the
wrong template name.

This feature is behind a feature flag `issue_zoom_integration`.

To enable this feature flag do:

    echo 'Feature.enable(:issue_zoom_integration)' | rails console

- Also includes db migration to track duplicated reference

Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>

When the user has permissions (ie. maintainer) they can follow this link
to the cluster page. Otherwise they can always view this cluster name.
This is to implement
https://gitlab.com/gitlab-org/gitlab-ce/issues/55095 and helps users
debug cluster deployments.

* Allow editing during rule creation
* Add Changelog entry
* Updates the backend to prevent the `License-Check` rule name from
being edited.

- Display an error illustration in case the
API responds with 403 for a given group_id
- Update PO file
- Update sepcs
- Add changelog entry

Updated the tab label to configuration

Finishes #13655

This change updates the text of the pipeline widget that appears on the
merge request page. The text has been made more consistent between
different types of pipelines; this makes the front-end implementation
simpler and more maintainable.  In addition, the type of pipeline is
(i.e. regular pipeline, merge request pipeline, detached pipeline)
included in the text, making this type more obvious to the end user.

Some information has been removed from the widget as part of this
change; however, any information that was removed already appears
elsewhere on the merge request page.

This change updates the text of the pipeline widget that appears on the
merge request page. The text has been made more consistent between
different types of pipelines; this makes the front-end implementation
simpler and more maintainable.  In addition, the type of pipeline is
(i.e. regular pipeline, merge request pipeline, detached pipeline)
included in the text, making this type more obvious to the end user.

Some information has been removed from the widget as part of this
change; however, any information that was removed already appears
elsewhere on the merge request page.

In the Merge Request view, under pipelines tab
the user can see a run pipeline button

Adds axios post request to button click

Adds the logic to handle the user click,
refresh the table and disable the button while thee
request is being made

Updates UI for desktop and mobile

Adds specs
Regenerates potfile

Follow-up after review

Uses .finally to avoid code repetition

The operations dashboard feature was brought from Ultimate to Premium
in GitLab 11.10
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10586.

This renames some missing items from Gold to Silver.

In the Merge Request view, under pipelines tab
the user can see a run pipeline button

Adds axios post request to button click

Adds the logic to handle the user click,
refresh the table and disable the button while thee
request is being made

Updates UI for desktop and mobile

Adds specs
Regenerates potfile

Follow-up after review

Uses .finally to avoid code repetition

* Add toast message for add/edit/delete dismissal reasons

Message about current plan should include username of the current user

It adds an upgrade button to the user billings
page that redirects to the customers portal
upgrade checkout page.

If the user is not logged in at the portal he/she
will be automatically redirected after the login
process.

If the user is at the latest tier, the button
won't be presented and it'll fallback to the
existing plans table.

It adds an upgrade button to the group billings
page that redirects to the customers portal
upgrade checkout page.

If the user is not logged in at the portal he/she
will be automatically redirected after the login
process.

If the user is at the latest tier, the button
won't be presented.

- Add GlLink to empty state message of feature_flags.vue
- Update tests

It consists of two parts:

1. Redirecting users to the configured external storage
1. Allowing the external storage to request the static object(s)
   on behalf of the user by means of specific tokens

Part of https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6829

Added new button to launch the new
stage form for customisable cycle
analytics.

Move add stage button to vue component

Added basic test for add stage button

Move css to bootstrap classes

Removes scss styling that can be applied
via bootstrap classes and adds the relevant
classes to html elements

Added feature tests for add stage button

Moved add stage functionality to ee mixin

Created addStageMixin for the add stage
functionality needed in EE. Added a stub
mixin to the CE dir.

It consists of two parts:

1. Redirecting users to the configured external storage
1. Allowing the external storage to request the static object(s)
   on behalf of the user by means of specific tokens

Part of https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6829

- Introduce Vuex store
- Add bar chart component
- Add reusable constants
- Pass endpoint and empty state svg path via data props
- Update app component
- Add store modules for charts and global_filters
- Introduce store modules
- Resolve UX discussions