Update dependencies (NPM and others)

[deribaucourt]

Run npm update in every package to update the dependencies. Fixes a few security audit warnings.

[deribaucourt]

@WilsonZiweiWang from my experience, some tests failed due to calling devtool modify. With the updated poky, it seemed to download Uninative and build many recipes to patch sources which is extremly slow.
It looked like if we stay on the current poky version we were unaffected. It would be ok for now.

Maybe I'm wrong and the tests fail for a reason, but that's my thoughts so far.

[WilsonZiweiWang]

@WilsonZiweiWang from my experience, some tests failed due to calling devtool modify. With the updated poky, it seemed to download Uninative and build many recipes to patch sources which is extremly slow. It looked like if we stay on the current poky version we were unaffected. It would be ok for now.

Maybe I'm wrong and the tests fail for a reason, but that's my thoughts so far.

When the integration tests are skipped, the CI can consistently pass if a little more time is given to the unit tests, for example, 10 minutes of timeout.

Successful runs with integration tests skipped:
https://github.com/yoctoproject/vscode-bitbake/actions/runs/17841666750/job/50732404783
https://github.com/yoctoproject/vscode-bitbake/actions/runs/17841666750/job/50734311096
https://github.com/yoctoproject/vscode-bitbake/actions/runs/17841666750/job/50734781920

According to the logs from a previous CI run and my local runs, they are all stuck at the reviewDiagnostics() from the integration tests. See this run where the integration tests spent hours at reviewDiagnostics(). I downloaded the logs in case they expire later:
15_Test Project.txt

[WilsonZiweiWang]

While the bitbake is scanning the project (/integration-tests/project-folder), multiple bitbake processes will spawn like the following:

zwang    1479052 12.5  0.4 208992 136632 ?       Sl   15:20   0:01 /usr/bin/python3 /home/zwang/projects/vscode-bitbake/resources/poky/bitbake/bin/bitbake-server decafbad 3 6 /home/zwang/projects/vscode-bitbake/integration-tests/project-folder/build/bitbake-cookerdaemon.log /home/zwang/projects/vscode-bitbake/integration-tests/project-folder/build/bitbake.lock /home/zwang/projects/vscode-bitbake/integration-tests/project-folder/build/bitbake.sock 0 0 None 0

In the meantime, the extension host is repeatedly trying to reconnect to the bitbake server:

The last attempt is when calling reviewDiagnostics() as shown in the log file I put in the above comment. Then it hangs forever as the bitbake server process no longer appears.

[deribaucourt]

Maybe we need to disable some test parallelization option that is new or reworded?