feat: allow setup for go-vet, govulncheck, and go-build

[CallumNZ]

Reference: https://github.com/GeoNet/tickets/issues/15422

In doing the above ticket^, I have found the reusable-go-apps workflow not very reusable at all. This change will align it more closely with its name.

Tested here, works: https://github.com/GeoNet/4D-Ashfall/actions/runs/9120866234/job/25079049471

[wilsonjord]

question: what cases would setups be different for build, vet, and vuln? I'm wondering if buildSetup could simply be used for all three workflows...

[CallumNZ]

@wilsonjord yes, I was wondering the same thing.

build,vet, and vuln would (or more accurately, should) always be the same.
test would be the same, but can often have extra things, so it makes sense to keep this separate.
fmt and imports don't care about the environment.

I would say lint would also be in the first group, but perhaps there's been a situation where it's not?
EDIT: we have never used lintSetup, so am removing it and feeding the buildSetup inputs to it instead.

[ozym]

Failed the commit conformance. It's quite strict.

[wilsonjord]

Perhaps go-test should be ${{ inputs.testSetup || inputs.buildSetup }}

[wilsonjord]

issue: I don't know if anyone uses this, but if they did, this is a breaking change

[CallumNZ]

I checked, no one uses it.

[wilsonjord]

lgtm