Upgrade to go 1.19

[crenshaw-dev]

Summary

Upgrade to go 1.19.

Motivation

There are new features/improvements. I'm particularly interested in go gc metrics reporting.

Proposal

The PR upgrading to 1.18 can be used as a guide.

We should document that plugins might be affected by this from the release notes:

Command and LookPath no longer allow results from a PATH search to be found relative to the current directory. This removes a common source of security problems but may also break existing programs that depend on using, say, exec.Command("prog") to run a binary named prog (or, on Windows, prog.exe) in the current directory. See the os/exec package documentation for information about how best to update such programs.

Plugin users might be relying on a binary being in the repo where the plugin is executed. v2.4 users won't be affected, because 2.4 strips executable permissions of repo contents before running plugins. But folks upgrading from previous versions might notice a regression.

(Note: try not to run binaries loaded via repos. That seems bad for security.)

[omarkalloush]

If this is as simple as upgrading to 1.18 I would like to do this please.

[crenshaw-dev]

@omarkalloush sure! If you want to do the upgrade part, I can add the plugin docs notes later. Let me know if you need any help.