Fix participants list padding

Closes #62432

See merge request gitlab-org/gitlab-ce!28873

Updated the padding to our standard size

Docs: Convert links in various docs to relative

See merge request gitlab-org/gitlab-ce!28967

Docs: Convert remaining links in /user to relative

See merge request gitlab-org/gitlab-ce!28964

Docs: Add introduced column to table in Personal Access Tokens doc

Closes #60531

See merge request gitlab-org/gitlab-ce!28874

Docs: Finish changing links to relative in user/project (part 2)

See merge request gitlab-org/gitlab-ce!28934

Docs: Change links to relative in /user/project (Part 1)

See merge request gitlab-org/gitlab-ce!28920

Docs: Clean up tables in permissions doc

Closes #59249

See merge request gitlab-org/gitlab-ce!28908

Limit milestones to before year 9999

Closes #58576

See merge request gitlab-org/gitlab-ce!28742

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'

Remove nils from project_statistics.packages_size

See merge request gitlab-org/gitlab-ce!28400

Now it defaults to 0

Setup Phabricator import

Closes #60562

See merge request gitlab-org/gitlab-ce!27877

delete group confirm popup mention projects deletion

Closes #62148

See merge request gitlab-org/gitlab-ce!28899

Externalize strings of Two-Factor Authentication page in user profile

See merge request gitlab-org/gitlab-ce!28749

Externalize strings of password page in user profile

See merge request gitlab-org/gitlab-ce!28744

Remove render_if_exists partial caveat

See merge request gitlab-org/gitlab-ce!28959

Open snippets visibility help link in a new tab

Closes #61911

See merge request gitlab-org/gitlab-ce!28603

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.

Generate letsencrypt private key on the fly

Closes #62452

See merge request gitlab-org/gitlab-ce!28855

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.

Consolidate documentation written for e2e tests under dev docs

See merge request gitlab-org/gitlab-ce!28572

Previously the documentation was separated.  If we want to bake
quality into the product, how better than to include everything
we use directly in the development documentation
Signed-off-by: ddavison <ddavison@gitlab.com>

Fix broken internal doc link

Move documentation for page objects to the e2e section

Merge remote-tracking branch 'origin/i18n-Two_Factor_Authentication-of-user-profile' into i18n-Two_Factor_Authentication-of-user-profile

Use Dockerfile flow for QA Auto DevOps

See merge request gitlab-org/gitlab-ce!28648

[QA] Allow login validation before creating personal access token

See merge request gitlab-org/gitlab-ce!28960

Move .html_safe outside of the _() so the parser picks up on the translation.