add go-test-coverage service link to PR template

[vladopajic]

this PR adds link to go-test-coverage in pull request template.

reasoning to include go-test-coverage are following:

• it provides the same level of functionality needed by repository owners (automated coverage check with badge display)
• it's free and open source
• it's easier to setup (no registration or permissions required)

[github-actions]

Thank you for contributing with awesome-go, we will revise your contribution as soon as possible.

Make sure you add the links in the body of the pull request that are requested in the contribution guide:

• godoc.org or pkg.go.dev
• goreportcard.com
• coverage

your project is about to be approved, it's under revision, it may take a few days

[vladopajic]

hello @avelino, could you review this PR? thanks!

[vladopajic]

hello @phanirithvij, could you review this PR?

[phanirithvij]

I am not sure about this. Many repositories don't use GitHub or GitHub actions and thus suggesting it to everyone isn't ideal.
What do you think @avelino

[vladopajic]

it's just additional option and developer can choose any method they would prefer.

[vladopajic]

@phanirithvij @avelino

here is some statistics: on randomly selected repositories (n=100) from awesome-go list

• 100 (all) repositories are using github
• 36 repositories don't use github workflow
  • 10 repositories don't have continuous integration at all

based on this statistics it looks like there are more repositories (~64%) that would already easily integrate with this tool (since those already use github workflow).
from another view, 100% of those repositories are hosted on github, using github workflow is as easy as adding file in repository root.

since users can choose any method they like, there isn't any problem is suggesting any method.

personally, it's much more uncomfortable to use SaaS solutions that are already listed.

[xhd2015]

not LGTM, we should not suggest using any specific tool