fix: correct linters-settings typo in .golangci.yml

[thevilledev]

The linter configuration had a typo ("linter-settings" instead of "linters-settings"), which prevented linter rules from being applied. Fixing this revealed and resolved multiple style issues across the codebase:

• Renamed shadowing parameter in net_unix.go
• Fixed import grouping in valueparser_test.go
• Corrected comment capitalization and spelling
• Unused parameters

[discordianfish]

Oops, good catch. Thanks!

[discordianfish]

Looks like there are still issues:

  Running [/home/runner/golangci-lint-1.60.2-linux-amd64/golangci-lint run  --verbose] in [/home/runner/work/procfs/procfs] ...
  Received 117687 of 117687 (100.0%), 0.1 MBs/sec
  Error: sysfs/vulnerability_test.go:44:38: `spectre` is a misspelling of `specter` (misspell)
  		{"Mitigation more special chars", "spectre_v1", &Vulnerability{CodeName: "spectre_v1", State: VulnerabilityStateMitigation, Mitigation: "usercopy/swapgs barriers and __user pointer sanitization"}, false},
  		                                   ^
  Error: sysfs/vulnerability_test.go:45:45: `spectre` is a misspelling of `specter` (misspell)
  		{"Mitigation with multiple subsections", "spectre_v2", &Vulnerability{CodeName: "spectre_v2", State: VulnerabilityStateMitigation, Mitigation: "Retpolines, IBPB: conditional, STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected"}, false},
  		                                          ^
  

[thevilledev]

Weird - I'm running latest golangci-lint version locally and it didn't catch this. Ran it on another machine and it did. Oh well, pushed a nolint fix since these refer to a vulnerability name. Should be fine now!

[discordianfish]

Thanks!