Rebased on main, force pushed.

The commit "Check for uin32 size with ParseUnit" was suggested by a linter. When I went to run tests on the generic worker with ./build.sh -t, a few go updates were applied to go.mod. I did not include these updates, but we may want to update the generic worker as well.

There's one more linter issue that I wanted @petemoore's feedback on before merging.

Rebased on main, force pushed.

The commit "Check for uin32 size with ParseUnit" was suggested by a linter. When I went to run tests on the generic worker with ./build.sh -t, a few go updates were applied to go.mod. I did not include these updates, but we may want to update the generic worker as well.

There's one more linter issue that I wanted @petemoore's feedback on before merging.

So looking at the warnings, they appear to be when strings are logged that are partly composed from data read in from the generic-worker config file. For example, in the generic-worker config file, the taskcluster root url property is set with the rootURL config setting. URLs are logged in the worker logs, that derive from this URL. Headers are also potentially logged, which will a one-time Authorization header, only valid for that particular request (so safe to log). But internally, it is signed by the access token, which originates from the user-provided generic-worker config file (where user in this since is the administrator that installed and configured the worker).

So I don't think any of these warnings are of particular concern, since a real user or task has no write access to the config file, and therefore cannot adjust values. If they could modify this file, we would have a much bigger problem, I believe.