Move to support Jupyterlab 3.3

[ajbozarth]

Jupyterlab 3.3 will bring select non-api changing features and fixes originally planned for 4.0

Elyra has been waiting on some of these features and fixes and this issue is to track that list of issues and track the update to use 3.3 if pinning to the new minor release is required

3.3 blocked issues:

• Remove Python 3.6 support #2374

Issues specifically blocked by jupyterlab/jupyterlab#11079

• Add support for const types in metadata editor #2269
• Make COS configuration optional in runtime configurations #2337
• Metadata tooling: support conditional schema property constraints #2338

Tracking Issue for back ported PRs to 3.3 jupyterlab/jupyterlab#11643

[ajbozarth]

@karlaspuldaro #2375 is blocked by jupyterlab/jupyterlab#10758 do you know if that PR is API breaking (meaning has to wait till 4.0)? Because if it isn't you can raise it on jupyterlab/jupyterlab#11643 to have it back ported to 3.3 and we'll add it here

[ajbozarth]

#1943 can be added to this if/when jupyterlab/jupyterlab#11540 is back ported to 3.3

[karlaspuldaro]

I believe #2375 is a 4.0 since we will be updating the libraries to v4

[karlaspuldaro]

#2019 can be added to this list

[lresende]

When doing this, could we also try running something like the code below (run from Jupyterlab source directory) to update the transient dependencies? Note that, as we are trying to update the lab dependencies as well, we should probably run twice, one with the regex filtering and one without:

jlpm run  update:dependency  --regex '^(@jupyterlab|@lumino|typescript|rimraf)' latest --regex --path ~/opensource/elyra/elyra