Auto update references for commits, tags, etc

[github-actions]

Automated changes by create-pull-request GitHub action

[deribaucourt]

@WilsonZiweiWang The vscode version should be aligned with the one contained in the client/package.json and server/package.json. Can we edit how the dependency bumps are generated to align all package.json files?

[WilsonZiweiWang]

@WilsonZiweiWang The vscode version should be aligned with the one contained in the client/package.json and server/package.json. Can we edit how the dependency bumps are generated to align all package.json files?

I think you meant to say the root package.json and client package.json because the server's package.json doesn't need vscode. In my research, the engine field indicates the minimum vscode version the extension is compatible with. If a user wants to run our extension, he must make sure his vscode is at least 1.92.0 or he will see an update button on our extension page telling him to update the vscode first. In our tests, we are testing our extension against the latest vscode, and it should be backward compatible.