CI: use BuildJet & self-hosted Windows runners

[DentonGentry]

1. Use buildjet for the longer Linux CI workflows.
2. Use a self-hosted Windows runner.
3. Split CIFuzz into three pieces to run in parallel.

Two runs each of the original workflow files and the updated workflows in this PR:

                                GitHub     GitHub     BuildJet  BuildJet   
cifuzz.yml                      8m 20s     7m 40s     4m 20s    3m 38s
codeql-analysis.yml             4m 30s     cached     2m 56s    2m 59s
cross-darwin.yml                3m 10s     3m 19s     1m 33s    1m 30s
cross-freebsd.yml               3m 33s     3m 10s     1m 28s    1m 22s
cross-openbsd.yml               3m 4s      2m 36s     1m 29s    1m 22s
cross-wasm.yml                  1m 59s     2m  2s     1m 12s    1m 16s
cross-windows.yml               2m 45s     3m  0s     1m 44s    1m 25s
linux32.yml                     4m 27s     4m  0s     1m 55s    2m  8s
linux-race.yml                  3m 54s     4m  7s     2m 22s    2m 12s
linux.yml                       4m 23s     4m 39s     2m 37s    2m 15s
static-analysis.yml
 /vet                           1m 41s     2m 22s        52s       56s
 /staticcheck(linux, amd64)     2m 47s     2m 38s     1m  7s    1m 10s
 /staticcheck(windows, amd64)   2m 5s      2m  4s     1m  6s    1m  8s
 /staticcheck(darwin, amd64)    2m 14s     2m 20s     1m 10s    1m 10s
 /staticcheck(windows, 386)     2m 36s     1m 58s     1m 23s    1m  8s
vm.yml                          1m 30s     1m 32s     2m 31s    2m 23s
windows.yml                     6m 23s     6m 19s     3m 40s    3m 53s

A few very short workflows are being left on GitHub-hosted runners, like licenses and gofmt.

Signed-off-by: Denton Gentry [email protected]