Can not access cluster UI for environments in a folder

Summary

The cluster UI view can not be accessed for environments that

• belong to a folder
• show up only behind the "Show all" button

Képernyőfelvétel_2023-09-19_-_21.16.29

Steps to reproduce

1. Configure more than 3 environments under a folder (e.g. dev/*)
2. Configure an agent in each
3. Check the environments
   1. The main environments page will list only the first three environments under the folder
   2. The main environments page will provide a "Show all" link to see all the environments
4. Click "show all"
5. Try to find the cluster UI

Example Project

• https://gitlab.com/gitlab-org/ci-cd/deploy-stage/demos/podtato-head-delivery/-/environments
• look for the environments under 'dev`

What is the current bug behavior?

There is no cluster UI.

What is the expected correct behavior?

There is a cluster UI shown.

The environment folder page views should be identical to the environments home page view.

Examples:

• environments home page view
• foldered environment list view

To simplify the experience, removing the accordion from folders, and making the default action to "open folder" would be ideal.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

As a quick fix it should be possible to switch from a table view we're using now, to using an EnvironmentItem component that's used on Environments page. It should make it possible to get access to k8s integrations.

The long-term solution is to unify both pages in a single implementation, described in this epic.

Things to pay attention to

We should check that all the controls associated with the environment are working properly, including starting/stopping of the environment, etc.