ss-1945 Changes to run Depictio with Gateway API

[j-awada]

Description

Jira: https://scilifelab.atlassian.net/browse/SS-1945

Changes in the Depictio app model type to enable running it with Gateway API.

Relates to: depictio/depictio#882

TODO

• Test changes on Serve dev
• Update Depictio chart version in fixtures/apps_fixtures.json
• Only merge this PR after Serve's v5.1.0-beta release

Checklist

If you're unsure about any of the items below, don't hesitate to ask. We're here to help!
This is simply a reminder of what we are going to look for before merging your code.

• This pull request is against develop branch (not applicable for hotfixes)
• I have included a link to the issue on GitHub or JIRA (if any)
• I have included migration files (if there are changes to the model classes)
• I have added or updated unit and end2end tests or a manual test case to complement my changes
• I have ran unit and end2end tests
• I have considered accessibility for UI changes and reviewed pre-commit/Pa11y results or documented a manual check
• I have updated the related documentation (if necessary)
• I have added a reviewer for this pull request
• I have added myself as an author for this pull request
• In the case I have modified settings.py, then I have also updated the studio-settings-configmap.yaml file in serve-charts
• In case your changes are large enough, did you deploy your changes to develop instance?

PR cheatsheet

• PR -- pull request
• Include jira ticket in the PR title (like SS-1234 Introduced machine learning ai driven framework for DDLS Fellows from EMBL)
• To set the status of the pull request, use the built-in github feature to set the PR as Draft or Ready for review.
• To indicate the type of change (such as bugfix or new feature), use a github pull request label.
• If pr is not ready for review, set it draft. We agreed in the team, that if the PR in the draft state, no one will review it.
• Remember, that you can trigger end2end tests manually

[hamzaimran08]

Do you think we need to do anything about k8s_values["backend"] and k8s_values["minio"] in apps/models/app_types/depictio.py as they seem to have separate ingresses?

[j-awada]

Do you think we need to do anything about k8s_values["backend"] and k8s_values["minio"] in apps/models/app_types/depictio.py as they seem to have separate ingresses?

They do, however httproutes get created for them from depictio's chart here or was there anything else that was missing?