* Adjust opened issues count in the milestone burndown chart
to match current opened issues in the milestone.
* Fix completion rate calculation to include milestones only.

- Select notification email by walking up group/subgroup path
- Add settings UI to set group email notification address
- Add tests

Change query to work on mysql as well. Also set entire date because setting only the year can trip 'start_date_should_be_less_than_due_date'

Now it defaults to 0

- Comply doc with guidelines
- Improve tests for readability and completeness
- Separate out phases visually with newlines
- Add `format_message` test
- test readability
- code and test structure/styling
- static query analyzers
- call `as_json` on `provided_variables`
- add exception handling

This sets up all the basics for importing Phabricator tasks into
GitLab issues.

To import all tasks from a Phabricator instance into GitLab, we'll
import all of them into a new project that will have its repository
disabled.

The import is hooked into a regular ProjectImport setup, but similar
to the GitHub parallel importer takes care of all the imports itself.

In this iteration, we're importing each page of tasks in a separate
sidekiq job.

The first thing we do when requesting a new page of tasks is schedule
the next page to be imported. But to avoid deadlocks, we only allow a
single job per worker type to run at the same time.

For now we're only importing basic Issue information, this should be
extended to richer information.

Remove migration generating lets encrypt key
Don't generate private_key if database is readonly

For reference:
This reverts commit 988a7f70489b99383b95e9f271a2caf6bb5b3a44.
This reverts commit 21acbe531592d55caf0e5b8716a3b551dafd6233.

We've already migrated all the legacy artifacts to the new realm,
which is ci_job_artifacts table.
It's time to remove the old code base that is no longer used.

So it's more modular and extensible

* Add Pipeline IID to MR's
* Add Pipeline IID to commit box
* Add Pipeline IID to builds page
* Add Pipeline IID to job sidebar
* Add Pipeline IID to header on view pipeline pages
* Add changelog entry
* Update tests

The ref to the branch was being displayed as
raw HTML in the Pipelines page

Tidy tests according to reviewer comments.
Move complexity and depth calls from `initial_value` to `final_value`
Log variables as json

- Add changelog file
- Fix failing tests

Remove instance variables for class re-use, test individual methods,
use `monotonic_time`

- Modify GraphqlLogger to subclass JsonLogger
- Replace the single-line analyser with one that can log all the GraphQL
query related information in one place.
- Implement analyzer behavior with spec

Specify dedicated logfile and logger class for GraphQL queries. Move
complexity analyzer to a dedicated class.

A new attribute was added to `GlPopover`, so the snapshots had to be
updated to match.

It assures that requests are aborted after 60 seconds, otherwise
an exception is raised. This exception is logged by Sentry, also
there is a Prometheus counter for measuring number of requests in each
state.

- On Operations settings page
- On Metrics dashboard page

This sampler gathers Puma-specific metrics which can be used by
Prometheus then.

Resolves https://gitlab.com/gitlab-org/gitlab-ce/issues/60107

Revert useless timeout added in karma spec

- adding a "Manual" option to the dropdown
- show 100 issues list when manually sorting

Extracts combining the job_artifacts relation with the with_reports
scope for getting report artifacts into a method.