Request to upgrade to newer version of git in default Codespaces image

[jaysee260]

An internal user brought up the fact that the current version of git installed in codespaces using kitchensink is a couple years old (2.25.1), and asked if we could bump this to a newer version.

One way to do this might be to update the default codespaces image to install a newer version of git.

Another way might be to upgrade the version of Ubuntu used by the kitchensink image to the latest LTS version, 22.04 (we currently use 20.04, which is the previous LTS version).

Whatever approach we take, because kitchensink is used by a lot of people using codespaces, we'd want to be cautious and make sure we don't introduce any regressions.

The purpose of this issue is mainly to raise awareness of this request, and for tracking purposes.

[samruddhikhandale]

For images, we are trying to rely on using the packages available upstream/OSS feeds (unless we need to patch a security vulnerability).

That said, as ubuntu:jammy is the current LTS we should update the universal image to use it.

I had already started working on updating current versions for tools/languages (to match LTS/latest). I'll include this change with it --> #267

[samruddhikhandale]

Just realized that oryx does not support ubuntu:jammy yet.

[huw]

Would it be possible to create a non-default tag of the universal image that makes a best-effort upgrade? I would like to be able to use a more modern toolchain (while keeping the special status this image has for the Codespaces storage quota) and don’t anticipate running into incompatibilities with the other tools.