This should fix the following error:

> The resource 'projects/freebsd-org-cloud-dev/global/images/family/freebsd-14-2' was not found

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

This is the latest supported Go version

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

ci: bump freebsd to 14.3

This reverts commit 5942541.

Pointer semantics on the caller are actually incorrect here: the
returned depthCounter is passed on to a deeper validation function, but
that shouldn't modify the original depthCounter from the caller. With
pointer semantics, we don't count e.g. the depth of array nesting, but
just how many arrays are present in the signature. For structs this is
especially bad since EnterStruct is called for each struct field, so
this unintentionally limited the number of struct fields that could be
present in a signature to 32.

Fixes #425.

Allow more than 32 containers / struct fields in a signature

It is no longer needed since commit 33c352a changed go to 1.20 in go.mod.

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

Those are no longer needed as the package requires Go >= 1.20
since commit 33c352a.

Generated by

	go fix ./...

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

Like this:

> object_test.go:71:7: ST1006: receiver name should not be an underscore, omit the name if it is unused (staticcheck)

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

As recommended by staticcheck linter, e.g.

> conn.go:448:3: QF1003: could use tagged switch on member (staticcheck)

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

As recommended by the staticcheck linter:

> variant_parser.go:295:2: QF1002: could use tagged switch on sig.str (staticcheck)

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

As recommended by the staticcheck linter, e.g.

> auth.go:60:14: QF1008: could remove embedded field "transport" from selector (staticcheck)

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

Bump golangci-lint to v2, fix some issues found

Since commits 99fac80 and ec919d8 it's clear that getHomeDir is only
used on Windows. Ironically, $HOME is not used on Windows (instead,
it's %USERPROFILE%), so we always fallback to user.Current, which
internally uses os.UserHomeDir to fill in HomeDir.

So, let's just use os.UserHomeDir directly (and fall back to "/" in case
of an error like the previous implementation did).

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

Fix and simplify getHomeDir