Extract code into IssueBoardEntity / serializer (follow up)

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

Support location.positions in code climate MR-widget

Closes #6813

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

AES-256-GCM cipher mode requires a key that is exactly 32 bytes long.
We already handle the case when the key is too long, by truncating, but
the key can also be too short in some installations. Switching to a key
that is always exactly the right length (by virtue of right-padding
ASCII 0 characters) allows encryption to proceed, without breaking
backward compatibility.

When the key is too short, encryption fails with an `ArgumentError`,
causing the web hooks functionality to be unusable. As a result, zero
rows can exist with values encrypted with the too-short key.

When the key is too long, it is silently truncated. In this case, the
key is unchanged, so values encrypted with the new too-long key will
still be successfully decrypted.

This reflects how we now create or update

If the service fails mid-point, then we should be able to re-run this
service. So, detect presence of any previously created Kubernetes
resource and update or create accordingly.

Fix specs accordingly. In the case of finalize_creation_service_spec.rb,
I decided to stub out the async worker rather than maintaining
individual stubs for various kubeclient calls for that worker.

Also add test cases for group clusters

We remove configure_project_service_account and replace
ClusterPlatformConfigureWorker as they perform exactly the same piece of
work. This also makes GKE cluster creation to be the same as Adding
existing cluster - they both now use another worker to execute
CreateOrUpdateNamespaceService.

Resolve "Bug: Avatar Icons have wrong tooltip in approval"

Closes #6309

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

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

Use new information-o icon for Security Dashboard

Closes #8506

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

Geo: Add LFS support to HTTP & SSH push to secondary specs

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

This reverts commit 22954f22

Geo: Fix push to secondary over SSH for LFS

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

Also remove repository_replication_spec.rb as it's more accurately covered by http_push_spec.rb

- Project#lfs_http_url_to_repo() returns #http_url_to_repo()
- EE::Project#lfs_http_url_to_repo() returns #http_url_to_repo() if isn't a Geo secondary with a primary, otherwise, returns Geo primary project HTTP URL
- Use Project#lfs_http_url_to_repo() in API /internal/lfs_authenticate

Added specs for #deploy_key_pushable?() and #type()

LfsToken::HMACToken#token_valid?() will be examined and if false, look
in redis via LfsToken::LegacyRedisDeviseToken#token_valid?().

Docs - Add 11.5 ES reindex info

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

Docs - Fix repository submodule API example

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

docs: Update code_quality.md

Closes gitlab-ce#51676

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