Note: I created a separate issue for a bug I detected within testing, please see eclipse-che/che#23486

What does this PR do?

• alignment with 1.100 release branch of the upstream: https://github.com/microsoft/vscode/tree/release/1.100
• fixes axios related errors: Align che-code typescript version with the upstream eclipse-che/che#23083 (comment),
  see also 3999823 and fix: Prevent multiple versions of axios from being bundled in consumer projects devfile/devworkspace-generator#201
• align typescript version with upstream fab39e3 and 77be1ed
• bump che-devworkspace-generator and axios versions 6bcef8c
• align playwright version with upstream dcf65f5
• use 20.19.x version of Node.js to prepare che-code assembly
• switches to 20.19.1version of Node.js for the Dev image 0181586
• fixes integration tests for the musl-based assembly c5d7ba3
• still can not align electron version, see chore: Align Node.js and proxy-agent versions with upstream #526 (comment)
• still can not align node-pty version because of electron version (see previous item ^): 724c0a9

What issues does this PR fix?

• Alignment Che-Code with 1.100.x version of VS Code eclipse-che/che#23428
• Align che-code typescript version with the upstream eclipse-che/che#23083
• Hot key does not paste text to the 'Search settings' field eclipse-che/che#23459

How to test this PR?

It makes sense to test both: ubi8 and ubi9-based assemblies.

Go to the dashboard => Create Workspace page => set quay.io/che-incubator-pull-requests/che-code:pr-547-amd64 to the Editor Image field and select a sample to start a workspace
or click
https://che-dogfooding.apps.che-dev.x6e0.p1.openshiftapps.com/dashboard/#/load-factory?editor-image=quay.io/che-incubator-pull-requests/che-code:pr-547-amd64&url=https://github.com/che-samples/web-nodejs-sample

1. Test any functionality, I tested the following:

• open a file
• create a default terminal
• create a terminal in a container
• instal an extension
• uninstall an extension
• run a devfile command
• run a command from the Command Palette
• Git Clone flow from the Command Palette

2. Restart workspace from a local devfile:

• start workspace with a devfile (there is a reference above for the web-nodejs-sample)
• open devfile.yaml file
• provide a change (I changed a command)
• F1 => Restart Workspace from a Local Devfile
• check that the change was applied (I run the command and tested that my change was applied)

3. Connect to Ansible lightspeed server form Ansible extension view:

I also tested the use case described in #532 to avoid a regression

4. Copilot-related items should be absent by default in the Command center area

I tested the use case described in #549

5. Hot key paste text to the 'Search settings' field

I tested that current PR changes fix the use case described in eclipse-che/che#23459

6. Released version of an extension should be installed

I detected a bug for the case when an extension contains another extension as a dependency, please see eclipse-che/che#23486

Does this PR contain changes that override default upstream Code-OSS behavior?

• the PR contains changes in the code folder (you can skip it if your changes are placed in a che extension )
• the corresponding items were added to the CHANGELOG.md file
• rules for automatic git rebase were added to the .rebase folder