fmt: introduce golangci-lint and go vet use CI with action and using build tag

[gen2thomas]

see #802 for a general description and the version without Github action
see #803 for version with multiple runners

This PR is an alternative way to earn all features of the golangci-lint GitHub Action.

This is achieved by adding a build tag to every file that cannot be linted due to a failed compilation. This is caused by dependencies to the "machine" package of tiny-go or other such dependencies (e.g. device/arm).

Although the condition is to add a build tag in many files, it has many advantages over the other versions:

• generic approach for running "go vet" and "golangci-lint" without any boilerplate code, locally (Makefile) and in CI
• incredible fast (takes 30 sec. only, compared to 7min for version with multiple runners)
• all features are fully supported (e.g. inline annotations)
• disable the linter by just adding a build tag in the file is possible in the future
• the same can be configured in each IDE (by adding to the local linter configuration)
• locally, if the IDE shows all linter issues, the developer can see it, although the package is disabled by build flag