Update Github Actions, cigolang-lint and apply linter

[selfhoster1312]

Upstream pull request: none
Other fork pull request: bibanon#21

There's still a lot of errors in the linter if you check the entire repo (instead of comparing errors with previous commits), but that's already better i guess?

To quote myself over there (changing the ref to the commit):

Sooooo i spent a few hours playing robot with my keyboard and monkeytyping stuff to get the CI working. I'm disabled a few imho useless lints, and there's just 2 left that don't pass and i think are important and require some level of review:

    musttag
    gosec

Otherwise on this branch golangci-lint should run without simply comparing errors with the previous commit which is a terrible way to accumulate tech debt and let it fall on the first person submitting a PR.

Feel free to review. In particular, this commit deserves special attention: https://github.com/matterbridge-org/matterbridge/commit/5fae6bc4e9607d3e65c4326e2fca2b2760bf48af

Because i have no idea what i'm doing in there i'm merely working around the linter errors and i don't know what's the idiomatic way to handle defer/goroutine errors in golang.

Let's see if the CI gods are with us!

[selfhoster1312]

Just seeing there's 35 commits to review and 88 changes files, maybe applying the lints right now on all the codebase is not the best idea after all. I'll open a smaller PR