Migrate users.private_profile to disallow NULL values

Closes #57538

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

This change sets NOT NULL constraint to users.private profile.

closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57538

Docs: Update Screenshots for protected tags and branches.

Closes #64574

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

CE-EE parity for root files

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

Add rubocop check for be success

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

Makes LFS object link process OIDs in batches

Closes #66274

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

Apply bindings to queries from QueryRecorder

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

- local tests that assume certain parameters to queries from
  QueryRecorder fail. These same tests don't fail in the runners,
  and I can't tell why. This fixes the local failures

Upgrade Mermaid to v8.2.4

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

Remove token field from runners edit form

Closes #35060

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

Add changelog entry

Remove unnecessary test checking for form value

Translations updated for gitlab.pot

Use proper format on changelog entry

Change the way totalNotes is calculated

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

Fix moving issues API failing when text includes commit URLs

Closes #66666

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

When a issue is moved from one project to another, all associated
Markdown text is rewritten in the context of the new project. If the
note contained a link to a commit URL, `CommitRewriter#rewrite` would
fail because `Commit#link_reference_pattern` would match `nil` `commit`
values in the HTML generated from the Markdown. These `nil` values were
passed along to `Project#commits_by` because `Commit#reference_valid?`
was always returning `true`.

To prevent this issue from happening, we tighten up the check for
`Commit#reference_valid?` to look for valid SHA values.

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

Improve specs output readability by replacing
`it_behaves_like` with `include_examples`
in `BeSuccessMatcher`

Adjusts snowplow to use cookies for sessions

Closes telemetry#77

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

This also restructures how and where the configuration for
Snowplow lives.

Rename all filenames and occurrences to License Compliance

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

- New redirect doc/user/application_security/license_compliance/index.md
- Renaming of images.
- Some links that were pointing to the old location are fixed.

Former shared examples were used only once.
Inlining them makes tests more clear.

Use Rubocop's Include
instead of manually checking the matcher in controllers specs.

BeSuccessMatcher now supports following examples:

```
expect(response).to be_success
expect(response).to_not be_success
expect(response).not_to be_success

is_expected.to be_success
is_expected.to_not be_success
is_expected.not_to be_success
```

Prevent using `be_success` call in controller specs to avoid
getting following deprecation warning:

```
DEPRECATION WARNING: The success? predicate is deprecated and
will be removed in Rails 6.0.
Please use successful? as provided by Rack::Response::Helpers.
```

Remove a section for a now fixed bug

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

Edit Feature Flags topic

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

Those guidelines where based on
https://gitlab.com/gitlab-org/gitlab-docs/issues/311 which seems
to be fixed.

Fix markdown in various docs (part 1)

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

Clean up issues that may cause the docs-lint
test to fail, such as trailing whitespace, no
EOF newline, blockquotes, etc

Fixes Introduced in text for our renderer

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

Note CI token exception to JWT requests in rate limit docs

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