multi: deprecation go get gocov

[petersssong]

Change Description

Description of change / link to associated issue.

go get currently modifies the go.mod file and that's probably not what you want installing a linter. Use go install instead.

ref:https://go.dev/doc/go-get-install-deprecation

Steps to Test

Steps for reviewers to follow to test the change.

Pull Request Checklist

Testing

• Your PR passes all CI checks.
• Tests covering the positive and negative (error paths) are included.
• Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

• The change is not insubstantial. Typo fixes are not accepted to fight bot spam.
• The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
• Commits follow the Ideal Git Commit Structure.
• Any new logging statements use an appropriate subsystem and logging level.

📝 Please see our Contribution Guidelines for further guidance.

[coveralls]

Pull Request Test Coverage Report for Build 13850600604

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage remained the same at 55.305%

---

Files with Coverage Reduction	New Missed Lines	%
btcutil/gcs/gcs.go	1	80.95%

Totals
Change from base Build 13794438730:	0.0%
Covered Lines:	29936
Relevant Lines:	54129

---

💛 - Coveralls

[guggero]

Thanks for the change. Though since goacc is declared as being deprecated now, I think we should use the native Golang coverage mechanism now. See lightningnetwork/lnd#9521 for an example.

[petersssong]

Thanks for the change. Though since goacc is declared as being deprecated now, I think we should use the native Golang coverage mechanism now. See lightningnetwork/lnd#9521 for an example.

got, Should we use the native Golang coverage mechanism in current PR, or open a new one?

[guggero]

I think you can change the PR title and content, so no need to create a new one.