Update URLs to better ones

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

Fix link for raising helm chart issues

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

Add link in K8s integration docs to RBAC roles

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

Docs: Update Variable naming

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

Fix error handling bugs in kubernetes integration

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

Use gitlab-ui in jobs and pipelines

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

Remove circular dependency on Redactable in migration

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

Resolve "GitLab Pages settings regressions"

Closes #48475

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

Updates clipboard button with gitlab-ui

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

Gitlab::BackgroundMigration::RedactLinks was prepending
EE::Gitlab::BackgroundMigration::RedactLinks, while
EE::Gitlab::BackgroundMigration::RedactLinks was trying to include
Gitlab::BackgroundMigration::RedactLinks::Redactable. Ruby 2.5.3 failed
with an uninitialized constant
(https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/118388511).

Fix alignment of diff comment buttons

Closes #53768

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

Fix DashboardHelper reference in spec

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

Helpers::DashboardHelper doesn't actually exist, and Ruby 2.5 gets rid
of the automatic top-level constant lookup
(https://bugs.ruby-lang.org/issues/11547).

Resolve possible cherry pick API race condition

Closes #53773

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

Enable even more frozen string in lib/gitlab

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

Symlinked hooks aren't executed

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

Ensure we create the secrets at the right time

Closes #53621

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

Previously, we just fetched the latest commit for the given branch when
presenting the resulting commit, but because something could have been
committed to that branch between the time we cherry-picked and the time
we render the result, the wrong commit could have been presented.

Now, we fetch the commit object with the commit SHA returned by the
commit change service, which should always be the correct commit.

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

Add revert to commits API

Closes gitlab-org/release/framework#48

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

Updates clipboard button component to use
the new glTooltipDirective and the new glButton
component from gitlab-ui

Improve Debugging Capabilities For Helm Application Installs

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

User can create a group level cluster and install applications

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

Add e2e test of push via HTTP via Git protocol v2

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

Remove created_at from WikiPage

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

Improve the Review Apps documentation a bit

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

In `deploy`, if the previous deployment failed, we delete/cleanup all
the objects related to the release, including secrets. The problem is
that if we create the root password before that, it will be then
recreated during the deploy with a random value!

By creatigng the secret just before actually deplying a new release, we
ensure that it won't be overriden.
Signed-off-by: Rémy Coutable <remy@rymai.me>

I have also extracted an issue in
https://gitlab.com/gitlab-org/gitlab-ce/issues/53738 to surface these
errors to users but now I am just fixing the bug where
kubernetes_namespace is undefined while handling this error

There is no reason to specially handle 404 here. We only handle 404
specifically if we are fetching something and want to return `nil` if
404.  This does not apply here.