feat: create data connector in project

[olevski]

This is the initial implementation.

Things that are missing:

• no tests
• the way that data connectors in projects are displayed is not right
• the backend is still a bit wonky and will not support everything (i.e. launching sessions fails)

/deploy renku-data-services=feat-add-project-as-dc-owner-pt2

[RenkuBot]

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

[lorenzo-cavazzi]

The PR changes make overall sense so far 👍 Some early comments inline.

In short, there is a better way to add types from the updated APIs from other repos branches, and there is some less-than-ideal prop drilling here -- tho the components you are touching here weren't the most straightforward and your solution looks acceptable in this case.

[lorenzo-cavazzi]

If these types are up-to-date in the renku-data-service branch feat-add-project-as-dc-owner-pt2, instead of creating an enhanced-api file, you should take the up-to-date spec file from there, overwrite the namespace.openapi.json file here and run the npm command npm run generate-api:namespaceV2.
We use the enhanced version mainly for extending the APIs -- usually transforming the response into a more convenient object (transformResponse) or using the tags to auto-refetch content (providesTags on GET and invalidatesTags on the other verbs)

[olevski]

They are not changed in the backend. But I think I will have to update them in the backend. For now I am kind of forcing the project namespace in a few places. And that is why I need this. I will remove this when it is fully integrated in the backend. I think I will be able to do this during the build.

[olevski]

This change is part of the following stack:

• feat: create data connector in project #3525 ◀
  • feat: proper listing of project data connectors #3528

_{Change managed by git-spice.}

[lorenzo-cavazzi]

Lgtm! 🚀

[RenkuBot]

Tearing down the temporary RenkuLab deplyoment for this PR.