Update links to golangci-lint documentation
MODIFY
build/scripts/find-lint.sh
build/scripts/find-lint.sh
# - `DENDRITE_LINT_CONCURRENCY` - number of concurrent linters to run,
# golangci-lint defaults this to NumCPU
# - `GOGC` - how often to perform garbage collection during golangci-lint runs.
-# Essentially a ratio of memory/speed. See https://github.com/golangci/golangci-lint#memory-usage-of-golangci-lint
+# Essentially a ratio of memory/speed. See https://golangci-lint.run/usage/performance/#memory-usage
# for more info.

MODIFY
docs/CODE_STYLE.md
docs/CODE_STYLE.md
In addition to standard Go code style (`gofmt`, `goimports`), we use `golangci-lint`
to run a number of linters, the exact list can be found under linters in [.golangci.yml](.golangci.yml).
-[Installation](https://github.com/golangci/golangci-lint#install) and [Editor
-Integration](https://github.com/golangci/golangci-lint#editor-integration) for
+[Installation](https://github.com/golangci/golangci-lint#install-golangci-lint) and [Editor
+Integration](https://golangci-lint.run/usage/integrations/#editor-integration) for
it can be found in the readme of golangci-lint.
For rare cases where a linter is giving a spurious warning, it can be disabled
for that line or statement using a [comment
-directive](https://github.com/golangci/golangci-lint#nolint), e.g. `var
+directive](https://golangci-lint.run/usage/false-positives/#nolint), e.g. `var
bad_name int //nolint:golint,unused`. This should be used sparingly and only
when its clear that the lint warning is spurious.

Update links to golangci-lint documentation (#1617)

Signed-off-by: Bohdan Horbeshko <bodqhrohro@gmail.com>