feat: add new apispec for the new amalthea sessions

[olevski]

This will be used only in Renku v2 with the new Amalthea operator.

[coveralls]

Pull Request Test Coverage Report for Build 10709956586

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 7 unchanged lines in 5 files lost coverage.
• Overall coverage decreased (-0.02%) to 90.572%

---

Files with Coverage Reduction	New Missed Lines	%
components/renku_data_services/base_models/core.py	1	91.4%
components/renku_data_services/connected_services/db.py	1	82.18%
components/renku_data_services/crc/db.py	1	87.81%
components/renku_data_services/storage/blueprints.py	1	94.76%
components/renku_data_services/crc/blueprints.py	3	93.19%

Totals
Change from base Build 10701549852:	-0.02%
Covered Lines:	9290
Relevant Lines:	10257

---

💛 - Coveralls

[andre-code]

The API specification looks good overall. Aside from my comment below, it handles all the cases currently used for Renku 2.0.

[andre-code]

Which part here represents the sessionId?

[olevski]

It's the name field.

[olevski]

This change is part of the following stack:

• feat: add new apispec for the new amalthea sessions #360 ◀
  • feat!: expand environments specification #338
    • feat: run notebooks in data service #375
      • feat: use cloud storage from amalthea #387
        • feat: perf improvements for amalthea sessions #411

_{Change managed by git-spice.}

[olevski]

@andre-code I have addressed all your comments. The other change in addition to the changes from your comments is that now the status is simpler as we discussed during the status update yesterday.

Now all you get to track progress is the number of total containers and the number of ready containers.

Please note that once a session is created the total number of containers may be zero for the first few request as the session is getting created and things are being created. But after 1 or 2 requests the number will be good. I can fix this it just requires a bit more changes on the amalthea side.