Replace react-virtualized with react-virtuoso for React 18 compatibility

[msujew]

What it does

Fixes a problem which came up during the React 18 upgrade (#11455). Removes the need for the react resolutions and replaces the outdated react-virtualized package with the react-virtuoso package. Although the react-window package is a spiritual successor to the react-virtualized dependency, it's missing many features which were needed for our tree rendering pipeline (namely measuring elements and caching these measurements).

Also fixes #11376 accidentally in the process. I just wanted to test the "endless list" option of the react-virtuoso package.

Also aligns the scrolling behavior of trees to vscode (it always scrolls selected elements into the center if they aren't visible).

• IP due diligence for @virtuoso.dev/urx

How to test

1. Perform manual smoke tests on tree widgets throughout Theia. There shouldn't be any regressions compared to the use of react-virtualized.
2. Open the History view and assert that the view only loads a hundred commits at a time (and more once you reach the bottom of the list).

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• As a reviewer, I agree to behave in accordance with the review guidelines

[colin-grant-work]

Smoke tests look good 👍. I think I'd be inclined to merge sooner rather than later to give more time to catch any bugs.

[colin-grant-work]

(Though I'd also like CI to run and pass...)

[msujew]

@colin-grant-work I'll rebase, but the 3PP dash license CI fails anyway, since the @virtuoso.dev/urx package license cannot be detected correctly by the check script. It somehow believes the package to be named just virtuoso.dev. See here and this due diligence issue. I confirmed that it's MIT, is it alright to put it in the baseline json manually? (see also the clearlydefined entry for the package) @vince-fugnitto any idea?

[vince-fugnitto]

@msujew it is probably fine to add it to our baseline for now given that the tool itself cannot parse the package's name. I do not see results for the package at that version on clearlydefined so we could also wait to see what Wayne says.

[msujew]

@vince-fugnitto Yeah I also had troubles finding it on clearlydefined. But adjusting the URL did the trick for me and it shows as MIT only. See here.

[anavarre]

Also fixes #11376 accidentally in the process. I just wanted to test the "endless list" option of the react-virtuoso package.

I know this has long been merged but with 1.29 I'm still very much seeing the max count is not respected. Should we reopen #11376?