feat: add builder type for session launchers

[leafty]

PR stack:

• (this) feat: add builder type for session launchers #3491
  • feat: get build status and trigger builds #3529
    • feat: show last build's logs #3534
      • refine: improve the selector fields for repo-based environments #3536
        • feat: add app params for image builders #3511

Closes #3490.

Add support for repository-backed session environments.

Note that, at this stage, images are not being built and that the UI is not checking the build status of the session environment yet.

/deploy #notest renku=build/session-env-builders renku-data-services=kpack-resources

[RenkuBot]

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

[leafty]

@andre-code

When editing a custom + build environment, the advanced settings form displays. Why is it not shown when creating the launcher?

The advanced settings are not editable for now when selecting "Create from a code repository". The values (e.g. port, URL path, uid, gid) are configured by the backend.

I couldn't test the functionality in the current deployment due to an error

The value of the option changed in the backend. Fixed now.

[andre-code]

Once I noticed a couple of issues while testing:

• Once the launcher is created, if the user tries to modify it, the advanced fields are visible. However, updating those values in the form does not reflect the changes in the environment card, and the values don't seem to be saved. Is this the expected behavior?

If the container image needs to exist first, perhaps those fields shouldn't be available to avoid confusion.

• There is a bug in the custom + build case. When updating a value in the edit form, the repository is unexpectedly changed when saving the form.

[leafty]

• Once the launcher is created, if the user tries to modify it, the advanced fields are visible. However, updating those values in the form does not reflect the changes in the environment card, and the values don't seem to be saved. Is this the expected behavior?

If the container image needs to exist first, perhaps those fields shouldn't be available to avoid confusion.

Advanced settings removed. They were removed in a later PR. This PR was created before the backend was ready and it was known that users cannot edit the advanced settings.

• There is a bug in the custom + build case. When updating a value in the edit form, the repository is unexpectedly changed when saving the form.

Can you post which browser you are using? I cannot reproduce this issue. When I select the edit option, the selected repository is the one that was saved before.

Fixed in 2fb83cf.

[andre-code]

Great work, @leafty 🎉 I tested the feature, and it successfully creates/edit the custom + build launcher as expected.

[RenkuBot]

Tearing down the temporary RenkuLab deplyoment for this PR.