Only display time if the job has deployed

Update JS tests for displaying job deployment time

Simplify boolean check in deployedDate

Disables the vue-i18n eslint rules for files
that are not able to be autofixed, this will
stop these offences causing pipeline failures
but they will need manual fixing.

i18n linting for .vue files under the
app/assets/javascripts/environments directory

As Auto DevOps deployments both label and annotations, that will be
included in the deploy board so need to warn at all.

Move the table paginaiton component under the
new pagination folder in vue shared components
and updates all the paths

Deletes unused CSS
Moves prometheus selectors into a prometheus file

Before this commit, environments grouped together in a "folder" would
include the folder name in the UI.  This information was unnecessary
since the folder is also shown in the UI.

In addition, this commit also makes some minor changes to how tooltips
are displayed for both environments and folders.

Creates helpers file
Cleans up tests

Creares a mixin & moves the EE template
differences into CE

Creates a mixin to include the ee only properties

Async loads EE components
Creates a Mixin for EE properties

Use plain job name in the "Deploy to..." dropdown
Both in the old haml template and in the new vue component

Andrew Fontaine authored 6 years ago and Filipa Lacerda committed 6 years ago

Ensure a vue.js component to confirm the re-deployment/rollback of an
environment pops up when rollback/re-deploy has been clicked so the user
must confirm their actions before accidentally rolling back or
re-deploying an environment.

Only on the `environment-table` view.

This commit fixes two problems:

1. When a user clicked on another page, the app would fetch the new page
data but never update because the request and response parameters failed
to match the isEqual check. This was happening because the JSON response
omitted the `nested` attribute, so there was a comparison with a `null`
value.  We fix this by scrubbing undefined values before doing the
comparison.

2. There were duplicate requests made for the environments page because
the success handler of fetchPipelines() would cause the polling
component to make another XHR request.

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

Ensure folders push to the top, if both have no last update, sort by
name.

The sorting algorithm should sort in the following priorities:

1. folders first,
2. last updated descending,
3. by name ascending,

the sorting algorithm must:

1. Sort by name ascending,
2. Reverse (sort by name descending),
3. Sort by last deployment ascending,
4. Reverse (last deployment descending, name ascending),
5. Put folders first.

It is done this way, as `underscore`'s sort API is very basic: simple
comparisons, sorting by ascending only.

To support environment folders in the UI on the Environments List
page, the environments index route previously returned one environment
per folder, excluding those other than the latest deploy. However, the
environtments dropdown on the metrics dashboard requires that any
environment be selectable.

To accommodate both use cases, support an optional 'nested' parameter
in the index route to return either a flat, complete response or a
nested response based on the use case in question. The new default
response structure is the flat response.

Upgrades prettier to 1.15.3
Runs `yarn prettier-save-all` against the codebase
Most changes are due to https://github.com/prettier/prettier/pull/5519

Allowing the EE to override a helper function to pass more data to vue

Here is another line that prettier changed in ee.