Replace ck8s with Welkin in tests

[anders-elastisys]

Warning

This is a public repository, ensure not to disclose:

• personal data beyond what is necessary for interacting with this pull request, nor
• business confidential information, such as customer names.

What kind of PR is this?

Required: Mark one of the following that is applicable:

• kind/feature
• kind/improvement
• kind/deprecation
• kind/documentation
• kind/clean-up
• kind/bug
• kind/other

Optional: Mark one or more of the following that are applicable:

Important

Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

• kind/admin-change
• kind/dev-change
• kind/security
• [kind/adr](set-me)

What does this PR do / why do we need this PR?

The end-to-end tests for Grafana failed as they look for Compliant Kubernetes in the welcome dashboard, which has been updated to use Welkin:

# cypress run: /home/anders/ck8s/compliantkubernetes-apps/tests/end-to-end/grafana/authentication.cy.js
ok 1 grafana admin authentication can login via static admin user
ok 2 grafana admin authentication can login via static dex user
not ok 3 grafana dev authentication can login via static admin user
# (from function `fail' in file /usr/local/lib/bats/support/src/error.bash, line 40,
#  from function `cypress_test' in file end-to-end/grafana/../../bats.lib.bash, line 262,
#  in test file end-to-end/grafana/authentication.gen.bats, line 27)
#   `cypress_test "grafana dev authentication can login via static admin user"' failed
# AssertionError: Timed out retrying after 10000ms: Expected to find content: 'Welcome to Compliant Kubernetes' but never did.

This PR updates the test to fix this.

• Fixes #

Information to reviewers

Checklist

• Proper commit message prefix on all commits
• Change checks:
  • The change is transparent
  • The change is disruptive
  • The change requires no migration steps
  • The change requires migration steps
  • The change updates CRDs
  • The change updates the config and the schema
• Documentation checks:
  • The public documentation required no updates
  • The public documentation required an update - [link to change](set-me)
• Metrics checks:
  • The metrics are still exposed and present in Grafana after the change
  • The metrics names didn't change (Grafana dashboards and Prometheus alerts required no updates)
  • The metrics names did change (Grafana dashboards and Prometheus alerts required an update)
• Logs checks:
  • The logs do not show any errors after the change
• PodSecurityPolicy checks:
  • Any changed Pod is covered by Kubernetes Pod Security Standards
  • Any changed Pod is covered by Gatekeeper Pod Security Policies
  • The change does not cause any Pods to be blocked by Pod Security Standards or Policies
• NetworkPolicy checks:
  • Any changed Pod is covered by Network Policies
  • The change does not cause any dropped packets in the NetworkPolicy Dashboard
• Audit checks:
  • The change does not cause any unnecessary Kubernetes audit events
  • The change requires changes to Kubernetes audit policy
• Falco checks:
  • The change does not cause any alerts to be generated by Falco
• Bug checks:
  • The bug fix is covered by regression tests

[aarnq]

LGTM