[DPE-3104] Create Jupyter notebook image

[deusebio]

This PR re-integrates jupyter (that is integrated with spark) that was removed from the image in #57, but in a dedicated image. I have also updated the CI pipeline such that when we release the base image, we also release the jupyter one.

I have discussed offline with @cjdcordeiro to make sure that the name of the image, charmed-spark-jupyterlab4:3.4-22.04_edge makes sense and it is sound.

[cjdcordeiro]

just to recap, the other option would be something like charmed-spark3.4-jupyterlab:4. I actually prefer that one, just because the image's entrypoint is jupyter, and thus it is more intuitive for the oci tag to reflect the entrypoint app's version.

Having said that, given that the rock comprises 2 main application components, I'll let you decide on what best fits your use case.

[welpaolo]

Looks good to me

[deusebio]

I have been discussing this topic offline with @cjdcordeiro and @kimwnasptd. In the case of compounded images (e.g. as in this case where we do have multiple components), each with its version, we came up with a couple of options for naming schemes to deal with this, that are summarized below. These options are meant to confirm with the current standard of naming tags of images with

<appVersion>-<base>_<risk>

Let's say that we have an image with 3 components, and respective versions: app-X.x , foo-Y.y and bar-Z.z. Two possible naming schemes are:

• app-fooY.y-barZ.z:X.x-base_risk
• app-foo-bar:X.x-Y.y-Z.z-base_risk

We would generally be inclined to go with the first, as this would provide clearer information about which app the appVersion refers to.