The `finish_loading` method waits for an element within another
element not to have the css selector `.fa-spinner`, but the ele-
ment used in the `wait_assignees_block_finish_loading` method
always has this class within the element with the following css
selector `.qa-assignee-block`, which makes the `finish_loading`
method not useful for this specific case, but the selector
`.qa-assignee-block .fa-spinner.block-loading` is only shown while
the block is loading, and then such an element is removed from the
DOM.

I noticed the new test that uses the method
`wait_assignees_block_finish_loading` failing on CI, but I could
not reproduce the issue locally, so, this change is a try to fix it.

Also, reorder some views to keep the standard of organizing things
alphabetically.

And prettify one of them due to static analysis violation.

Links to SHA commits on the Releases page

See merge request gitlab-org/gitlab!16128

Modify the Release API endpoint and Vue components to add live
links on the Releases page.

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

Productivity Analytics: Introduce fetchSecondaryChartData action

See merge request gitlab-org/gitlab!17347

- This fetches data for all charts except for the main chart

Only use basename from $BACKUP variable

See merge request gitlab-org/gitlab!16464

This is the documented intention of this variable and protects against
path traversal attacks, which are low-risk though because the variable
is only used in a Rake task and under administrator control.

Added when Zoom quick actions will be available

See merge request gitlab-org/gitlab!17535

Move SMAU usage counters to the UsageData count field

Closes version-gitlab-com#158, version-gitlab-com#159, version-gitlab-com#149, version-gitlab-com#148, version-gitlab-com#150, version-gitlab-com#147, version-gitlab-com#157, and version-gitlab-com#146

See merge request gitlab-org/gitlab!17074

In other MRs we added some counter as independent params
in the usage data json we use. Nevetheless, they should
be gathered together inside the `count` field in the
`UsageData` model.

Use the redis set cache for branch and tag names

Closes #30439

See merge request gitlab-org/gitlab!17116

Enable uploading of SVG images for Design Management

Closes #12771

See merge request gitlab-org/gitlab!16160

Adjust unnapliable suggestions in expanded lines

See merge request gitlab-org/gitlab!17286

Empty state for when there's no files found in search

See merge request gitlab-org/gitlab!16851

Update docs for repository push audit events

Closes #13986

See merge request gitlab-org/gitlab!17013

[Docs] Add datetime_with_timezone to the migrations guide

See merge request gitlab-org/gitlab!17534

This reverts commit 034f0340.

Migrate dropdown_spec to Jest

Closes #31628

See merge request gitlab-org/gitlab!16913

Closes https://gitlab.com/gitlab-org/gitlab/issues/31628

When expanding diff lines and leaving suggestion comments,
eventually, they showed as unnapliable
even with no changes in the diff.

It happened given the `DiffNote#supports_suggestion?` check was
being made at `Suggestion#appliable?` in the discussions iteration.

The problem with `DiffNote#supports_suggestion?` as it is that
it uses `Position#diff_file`, which has a RequestStore "cache".

So for instance, if we have 3 comments in expanded diff lines
for the same diff file, just the _first_ expansion would be
considered, therefore, just the _first_ suggestion within
this set of comments on expanded lines would be
appliable.

All in all, we're able to simply remove this check from the
`appliable?` method given we already check if the note supports
suggestions uppon creation (`Suggestions::CreateService`).

As an extra outcome, we'll submit less Gitaly requests.

Expose cycle analytics stages and events

See merge request gitlab-org/gitlab!16240

This commit exposes a JSON endpoint to retrieve the available cycle
analytics stages and possible events for a given group.

Move stray changelog to correct place

See merge request gitlab-org/gitlab!17461

Automatically run 'schedule:package-and-qa' on .com schedules

See merge request gitlab-org/gitlab!17237

Resolve "Improve and migrate FE registry Karma tests to Jest"

Closes #30238

See merge request gitlab-org/gitlab!16827

Reachable code fully covered

Fix bug that caused a merge to show an error message

Closes #32477

See merge request gitlab-org/gitlab!17466

Update issue template to not mention CE and EE repos

See merge request gitlab-org/gitlab!17502

Find namespace by env name instead of slug

See merge request gitlab-org/gitlab!17271

The problem with using slugs is that we already have persisted
environments matching generic branch names but different slugs.
Environments are uniquely identified by by `(project_id, name)`, so this
should be just as safe.

See https://gitlab.com/gitlab-org/gitlab/issues/32341

Update issue templates to use new links to the GitLab project
after it has been moved

Rename CreateItemForm component to CreateEpicForm in epics tree

See merge request gitlab-org/gitlab!17249