chore: selenium tests to install CLI version fetched from core

[jachro]

This PR changes the behaviour of selenium tests in a way that they call the /api/renku/apiversion API and read the new cli_version property. This way the tests will always use CLI that is compatible (in fact the same) as installed on renku-core.

NOTICE:

• this PR cannot be merged before chore(service): return cli version in core svc renku-python#3655 is merged and released
• a following env var definition has to be taken out from the helm-chart/renku/templates/tests/test-renku.yaml; it cannot be done now as it will be brought with Update from auto-update/renku-graph-2.47.1 #3370.

      {{ if .Values.global.renku.cli_version }}
      - name: RENKU_CLI_VERSION
        value: '{{ .Values.global.renku.cli_version }}'
      {{ end }}

/deploy

[RenkuBot]

You can access the deployment of this PR at https://ci-renku-3379.dev.renku.ch

[rokroskar]

@jachro @Panaetius we should be able to merge this?

[jachro]

@jachro @Panaetius we should be able to merge this?

A good question. I updated the PR and took out the link to renku-python branch. Let's see.

[jachro]

The selenium mtests run and failed as the response from https://ci-renku-3379.dev.renku.ch/api/renku/apiversion

{"result":{"maximum_api_version":"2.2","latest_version":"2.9.1","supported_project_version":10,"minimum_api_version":"1.0"}}

didn't contain the expected cli_version property. @Panaetius was that change adding the property part of the lastest release on renku-python?

[rokroskar]

@Panaetius I guess we can close this?

[RenkuBot]

Tearing down the temporary RenkuLab deplyoment for this PR.