Refactored issue tealtime elements

See merge request !11242

Import export users select

See merge request !11286

Use .trigger(‘click’) instead of .click

See merge request !11317

Move copy button after commit sha

Closes #29168

See merge request !11303

Fix new branch dropdown position and size

Closes #32096

See merge request !11279

Fix redirect message for groups and users

See merge request !11313

This is to improve reliability on mentioned tests

Fix displaying a repository without a readme

Closes #32122

See merge request !11312

Remove unnecessary cache definition in rake karma test

Closes #32119

See merge request !11306

Closes #32119

Set correct docsUrl in pipeline schedules callout component.

Closes #31957

See merge request !11216

Update copy on Create merge request dropdown

See merge request !11304

Fix overlapping lines in SVG

Closes #32091

See merge request !11299

Remove balsamiq module from common_vue bundle

Closes #32092

See merge request !11248

Add missing tear down of sidebarMockInterceptor

Closes #32020

See merge request !11204

Ensure filtered_search utilizes common_vue bundle

See merge request !11273

Link to commit author user page from pipelines

Closes #29368

See merge request !11100

Update DB requirements in the documentation

See merge request !11293

Clean up ci variables table

Closes #31799

See merge request !11186

Add a new column before creating rename triggers

See merge request !11297

Update installation.md - Updated the Ruby section.

See merge request !11251

fixed small typo - piplnie should be pipeline

See merge request !11296

POC: Use position sticky on merge request tabs

See merge request !11289

MySQL doesn't allow us to create a trigger for a column that doesn't
exist yet. Failing with this error:

```
Mysql2::Error: Unknown column 'build_events' in 'NEW': CREATE TRIGGER trigger_6a80c097c862_insert
BEFORE INSERT
ON `services`
FOR EACH ROW
SET NEW.`build_events` = NEW.`job_events`
```

Creating the new column before creating the trigger avoids this.

Add summary lines for collapsed details in the bug report template

See merge request !11280

Include blob content when printing page

Closes #31781

See merge request !11247

Enforced by the database, and no callbacks need to be called.

Combined with 7b9b2c6099 and 294a8b8a6d this resolves
gitlab-org/gitlab-ce#31799

Variables shouldn't exist without a project, so a foreign key was added
with CASCADE'ing effects.

This makes it more obvious that we greatly prefer PostgreSQL over
MySQL/MariaDB and that all users are recommended to use PostgreSQL
instead. This also removes the paragraph mentioning the size per user
row, as this is completely inaccurate and doesn't really help users with
anticipating the database size. Instead we now simply recommend users to
have at least 5-10 GB of storage at minimum.

[ci skip]

Moved the data into the data method
Renamed edited ago class name

To be more specific; key, and project_id. If either of these is
NULL its wrong, because:

1. storing a key value pair without key is just plain wrong
2. all variables should belong to a project

Non of these cases existed on the staging database.