Merge branch '9540-broken-master-due-to-spec-finders-merge_requests_finder_spec-rb-292-syntax-error-unexpected-keyword_end-expecting-end-of-input' into 'master'

Resolve "Broken master due to "spec/finders/merge_requests_finder_spec.rb:292: syntax error, unexpected keyword_end, expecting end-of-input""

Closes #9540

See merge request gitlab-org/gitlab-ee!9379

Docs serverless tmcli update

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

Merge branch '9465-geo-repositories-cleanup-worker-can-leave-orphaned-entries-in-the-tracking-database' into 'master'

Geo - Perform GeoRepositoryDestroyWorker even when repository does not exist

Closes #9465

See merge request gitlab-org/gitlab-ee!9344

Fix rubocop violations

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

fix(settings): Adjusted vertical alignment of visibility icons

Closes #39759

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

Fix flaky wiki create test

Closes gitlab-org/quality/nightly#24

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

Add nested param to ee env controller specs

Closes #9521

See merge request gitlab-org/gitlab-ee!9375

This got merged up somewhere in the process of merging dev.gitlab.org
and GitLab.com back together.

[ci skip]

In commit 6fa5fd85 the `require: false`
was removed to ensure the Gem was loaded at run time. Unfortunately, the
`require` necessary for the rubyzip Gem is "zip" and not "rubyzip". As a
result, Bundler would not require the Gem. This meant that we would
still run into constant errors when referring to `Zip::File`.

[ci skip]

pages:deploy step was failing with the following error:

```
unitialized constant SafeZip::Extract::Zip
```

Since license_finder already pulls in rubyzip, we can make it
a required gem. We also use the scope operator to make the reference to
Zip::File explicit.

[ci skip]

[ci skip]

Fix a JS race in a spec

Closes #56860

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

When a user is a guest user, and the "Public Pipeline" is set to false
inside of "Settings > CI/CD > General" the commit status in the project
dashboard should not be shown.

When moving a project, it's possible that some users who had
access to the project in old path can not access the project
in the new path.

Because `project_authorizations` records are updated asynchronously,
when we send the notification about moved project the list of project
team members contains old project members, we want to notify all these
members except the old users who can not access the new location.