Migrate Elyra extensions to support JupyterLab 4.x

[lresende]

What changes were proposed in this pull request?

Migrate Elyra extensions to support JupyterLab 4.x

Fixes #3137

How was this pull request tested?

Building and running on JupyterLab 4.x

Developer's Certificate of Origin 1.1

   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

[kevin-bates]

I'm assuming the build failures are a temporary hurdle. Thanks for dealing with the @lresende!

[lresende]

I have made some progress here, but I would appreciate if I could get some help on the UI pieces, in particular on UI-components... @marthacryan @karlaspuldaro @ajbozarth and others feel free to send prs to this branch as time permits... I completely understand if you are not able to.

[karlaspuldaro]

This line is causing build failure, maybe it's best to use a stable version of yarn

[hadesto]

hello! is this pull request still being worked on? it would be amazing to have support for JL4 now that JL3 has an official sunset date. Is there any support required from the community? Thank you!

[lresende]

There is a pr against this pr, let me merge that over the weekend and then others can jump in to help finish any remaining items

[hadesto]

thanks for the quick response!

[ederign]

hi @lresende, thank you so much for this work! Where are these 'remaining items' located? I would love to figure out ways to help! (at least testing it)

[harshad16]

thank you so much for this work! Where are these 'remaining items' located? I would love to figure out ways to help! (at least testing it)

@ederign they are opened as PR to the branch, here: lresende#1

[Ekzz0]

Hi @lresende, this migration still being worked on? should we expect changes in the near future?

[lresende]

@Ekzz0 we need to resolve some of these conflicts, but, at a high level, the branch is working with JupyterLab 4.2.5

[lresende]

I have rebased and resolved conflicts, also removed some unrelated changes that can come as another pr to simplify review... let's wrap this up.

[caponetto]

@lresende I've sent two PRs targeting your branch to make it green on the CI.

Please take a look at them when you have some time.

• Migrate R editor, Scala editor and Code Viewer extensions to JL4 lresende/elyra#3
• Fix tests for JL4 upgrade branch lresende/elyra#4

I think we should make the CI for this PR green first, and then work on details (for instance reverting those unrelated changes and/or fixing bugs).

[shalberd]

Ah, yes, that is the failed yarn cypress integration test again, the one that is flaky. Not flaky anymore, this time, though, Pipeline Editor tests partly failing. Still, much better than before already.
"Snapshot Match Error: Value does not match stored snapshot" expected content is null or empty, it seems.

[lresende]

@caponetto It seems like the last test issue is related to some properties not being saved on the pipeline files, which fail to match the existing snapshot. I noticed you made some changes in that area recently. Would you have some time to help identify what's going on?

[caponetto]

@lresende please see lresende#5

[lresende]

Thank you @caponetto , so are you saying that the empty fields are not being saved to pipelines anymore and it's ok to remove them? Particularly as it is working on main branch.

[lresende]

Thank you @caponetto , so are you saying that the empty fields are not being saved to pipelines anymore and it's ok to remove them? Particularly as it is working on main branch.

Never mind, I see the difference in the duplicate/different block.