go.mod, compiler: bump minimum Go version to 1.23

[jakebailey]

Having go1.22 in go.mod causes gotypesalias=0 to be the default, even if the other parts of the toolchain are Go 1.23+ or higher. Bumping the minimum version resolves this, and I added a test.

In searching for docs/CI to update, I found one TODO that said it should be done in 1.23+, so, I did that too.

Related: #4894

[jakebailey]

Hm, fun, I guess some of tinygo is not gotypesalias ready after all, and the go.mod version was masking it.

[deadprogram]

Also:

go: downloading github.com/tetratelabs/wazero v1.6.0
go: downloading gopkg.in/yaml.v2 v2.4.0
no Go files in /root/project/tests/testing
--- FAIL: TestBuild (0.00s)
    --- FAIL: TestBuild/Host (0.01s)
        --- FAIL: TestBuild/Host/typealias.go (4.32s)
            main_test.go:327: # command-line-arguments
            main_test.go:327: /root/project/testdata/typealias.go:4:6: generic type alias requires GOEXPERIMENT=aliastypeparams
FAIL
exit status 1
FAIL    github.com/tinygo-org/tinygo    74.794s

[deadprogram]

I would agree that we can bump the minimum version. Anyone else have any feedback before I squash/merge?

[deadprogram]

@jakebailey do you want to squash/rebase these commits yourself?

[jakebailey]

Sure, I just assumed you did that with GitHub squash merge itself.

[deadprogram]

Sure, I just assumed you did that with GitHub squash merge itself.

I think there are a couple atomic commits in this PR so better to not squash it all together into 1.

[jakebailey]

Rebased into two commits which should pass tests individually.

[jakebailey]

Hm, CI fails, but I think this is a flake? I did not change the code in the PR.

[aykevl]

If I understand correctly, by dropping Go 1.22 support we add support for type aliases? If so, yeah that seems reasonable.

[deadprogram]

Thank you very much @jakebailey for the improvements and to @aykevl for helping review. Now merging.