As per https://gitlab.com/gitlab-org/gitlab/-/issues/321511 we've seen
one of these tests fail. It seems likely the problem is caused by the
use of `X.days.ago` throughout and then filtering with date ranges. The
likely explanation is that when the test is running just before midnight
then `2.days.ago` actually ends up being "3 days ago" from a date
perspective by the time the assertion is made about it.

Even though it's not easy to replicate this exact failure mode and this
flakiness has never happened for this spec before (to my knowledge) in 3
years it still is not a good way to write these kinds of tests as this
is theoretically a problem.

Instead of making all the times relative to "now" (which changes) I've
just made everything relative to some arbitrary fixed time. This works
fine, without any need for freezing time, as none of the methods being
tested actually refer to the current time.

The test is still quite difficult to read due to many different dates
and times and the fact that the examples are separated from the test
setup but I don't think this change makes it less clear.

Fix flaky calendar spec by clicking the same cell again

See merge request gitlab-org/gitlab!54281

We recently added more tabs which pushed the tabs to the left
and meant the Overview tab is obscured by a tooltip.
So instead we now click, then wait, then click the same cell again
Unsure if it's actually supposed to behave like this, but it does

Remove ci_custom_yaml_tags feature flag [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!54198

Added maintenance mode to planned failover

See merge request gitlab-org/gitlab!53149

Add GraphQL mutation for configuring API fuzzing scans

See merge request gitlab-org/gitlab!53883

The mutation has all of its fields and arguments, but does not yet
contain any functionality.

Add an availability warning to junit screenshots docs

See merge request gitlab-org/gitlab!54270

Revert "Fixes GraphQL pipeline status notification with warnings"

See merge request gitlab-org/gitlab!54268

Wait for requests in `add_note` feature spec helper

See merge request gitlab-org/gitlab!54227

This might make some feature specs less flaky.

Also, remove a bunch unnecessary `wait_for_requests` after
calling `add_note`.

Remove "please" from top-level Gitaly doc

See merge request gitlab-org/gitlab!54110

Remove "please" from page, and other edits.

Modernize vocab in triggers doc

See merge request gitlab-org/gitlab!54195

Update Sample GitLab Project Template with MR conflicts fix

See merge request gitlab-org/gitlab!54248

Previous template mistakenly had MR conflicts and
would send emails to users

Remove needs from license_scanning job

See merge request gitlab-org/gitlab!54234

Update docs to remove incorrect admin wording

See merge request gitlab-org/gitlab!53577

Update the word admin to administrator and
similar, as needed.

This reverts commit b591dcbe.

Resolve "Flaky test spec/models/release_highlight_spec.rb[1:1:1:1]"

See merge request gitlab-org/gitlab!54200

Sort JavaScript imports

See merge request gitlab-org/gitlab!54259

Add follow each other model, API and UI(profile, activity view)

See merge request gitlab-org/gitlab!45451

Migration observer to report size change

See merge request gitlab-org/gitlab!53979

Relates to
https://gitlab.com/gitlab-org/database-team/team-tasks/-/issues/145

Refactor daily coverage specs

See merge request gitlab-org/gitlab!54081

Refactor(profile preferences): refactor rails eval [RUN-AS-IF-FOSS]

See merge request gitlab-org/gitlab!51218

Migrate rails eval'ed js to form event listeners

Update to Project Labels info

See merge request gitlab-org/gitlab!54100

Fix security dashboard for Safari (< 14.0)

See merge request gitlab-org/gitlab!54042

Enable ESLint rule import/order globally

See merge request gitlab-org/gitlab!54160

Sort latest changes from master

Correct role required to view email address

See merge request gitlab-org/gitlab!54129

The service desk internal email address appears to only be
available to maintainer roles or higher, not to every project
member (such as those with developer, or reporter roles
acting as support agents to the service desk feature)

Import epic award emojis when using Bulk Import

See merge request gitlab-org/gitlab!53747

Support caching in development environment

See merge request gitlab-org/gitlab!54103

Change usage of CI/CD variables terminology in package docs

See merge request gitlab-org/gitlab!54193