There are not that many uses of `localTimeAgo`, but we can move from
jQuery to native DOM selection.

We currently expose `window.timeago` and `window.gl.utils.localTimeAgo`.
As far as I can tell, they are not used like that anymore and any part
of the code base that still uses it like that should move to direct
imports.

This was actually the _last_ instance of a JavaScript file setting up a
`window.gl` side-effect. Unfortunately this breaks a lot of tests.
Therefore we add the `window.gl` sideeffect to our jest set up. And in
order to be 100% sure that we do not break production, we add the
sideeffect to main.js as well.

For the following sections:

- Service Ping consent alert
- Usage statistics settings

Changelog: changed

- Add hide-when-top-nav-open classes
- Set up eventHub for app component to use
- Puts placeholder content which will be
  filled in a follow up since this is behind
  a feature flag

Add Changelog

Update btn-default-toggle-comment.yml

Sort latest changes from master

Replaces old HAML + vanilla JS version of feature highlight
with the Vue component

See https://gitlab.com/gitlab-org/frontend/eslint-plugin/-/issues/18
for more information.

Sort JavaScript imports in the CE code
to match our future ESLint configuration.

Part of our prettier migration; changing the arrow-parens style.

Mandatory not to break master. Automatically created with prettier.

Ignores this for specs since we're mostly
concerned about this causing production issues.

Both fadeIn + fadeOut to make transition to jquery slim possible

Changed where possible to use gl-display-none

Went back to hide util class

Introducing more gl-display-none

Remove relevant backend parts and tests

Create a wrapper to initialize GlPopover instead of Bootstrap popovers
on elements that have the data-toggle="popover" attribute.

Replace all jQuery tooltip API calls with the
tooltips facade API

This fixes problems where users could click buttons before the event
handlers are setup.

Remove jquery-ujs and use rails-ujs instead

The search initialization errors on pages that don't have a search (e.g.
login, terms agreement page)

performance_bar is now its own Webpack bundle 
and only loaded when performance bar is activated
Fixed the performance_bar specs
Removed the lint about not having a linting failure

Creates an alert handler that will allow us to remove the bootstrap
alert code easier.

- the work being done in snowplow initialization
  was slowing down dom load times and deferring
  it here should speed it up a bit.

We currently initialize the Awards Handler on every page, this moves it
to the pages where it is used:
- Commits
- Epics
- Issues
- Merge Requests
- Snippets

This removes $.fn.glDropdown and replaces it with the function
initDeprecatedJQueryDropdown. This ensures that modules which rely
on this function are not dependent on a globally accessible function
and also prevents naming confusion with the gitlab-ui component
also named GlDropdown.

Replaces the default export flash
function with the newCreateFlash.

Fix outstanding flash imports

Updates specs and replaces outstanding
imports for `Flash`

Fixes additional specs

Updates the remaining calls to different
flash methods, except for the window.Flash
method since this will break .erb templates

Fixes Trailing Whitespace problem

We follow this imports order:
// 1. "external" modules
import _ from 'lodash';
import chalk from 'chalk';
// 2. "internal" and aliased modules
import foo from 'src/foo';
// 3. modules from a "parent" directory
import foo from '../foo';
import qux from '../../foo/qux';
// 4. "sibling" modules from the same or a sibling's directory
import bar from './bar';
import baz from './bar/baz';
// 5. "index" of the current directory
import main from './';

This reverts https://gitlab.com/gitlab-org/gitlab/merge_request/31187

This avoids an issue where the config function is not
called in the production bundle