feat: Go, NPM and Yarn detection

[timyarkov]

To increase the breadth of what macaron can detect, this PR adds detection capabilities for projects using Go, NPM and Yarn as their build tools. Note this does not include dependency resolution of these tools, only detection.

• defaults.ini defines the patterns for detection of Go, NPM and Yarn projects in the relevant sections
• Go detection looks for a go.mod file, with a build keyword of either build or install. Since go doesn't have any in-built publishing/deployment, the publisher is taken as using goreleaser with the deploy keyword release. In a similar vein to this goreleaser/goreleaser-action is the Github Action looked for.
• NPM detection looks for looks for a package.json/package-lock.json/.npmrc (whether to accept strange combinations of these like only having a .npmrc or something I'm going to assume is for later PRs), with a build keyword of build and a deployment keyword of publish. For github actions it looks for JS-DevTools/npm-publish
• Yarn detection looks for the same keywords as NPM detection, except instead of .npmrc it looks for .yarnrc (for yarn classic) or .yarnrc.yml (for yarn modern). For yarn classic the deployment keyword is still publish, but to support yarn modern the keyword npm publish is also supported. Also, it doesn't have any associated CI actions defined as of now.

Linked issues: #363 #443

To clarify before merging this PR:

• Having two go.mod files within the codebase seems to break the pre-commit hooks at least (for each go related hook it's an exit code of 1 with the only shown error go: warning: "./..." matched no packages), guessing it would break more stuff. Need to sort out this out some sort of way
• Need clarification on how to handle detecting deployment of Go projects, to ensure whether the approach is correct or not.
• Are there any Yarn github actions I have potentially missed during my research
• Need clarification on if NPM's github action is ok, mainly picked it since it seemed popular but it doesn't look like something official

[behnazh-w]

We should also add pnpm ,pnpm-lock.yaml, and the publish command.

[timyarkov]

We should also add pnpm ,pnpm-lock.yaml, and the publish command.

Should this be a separate class or is it alright to roll it in with npm (i.e. npm build tool looks for both npm and pnpm files)? Since far as I can see from a quick glance for purposes of this its more or less same as npm except for the command/lock file, so I feel like an extra class would be a lot of repeat code that would be a pain to manage in future

[behnazh-w]

Should this be a separate class or is it alright to roll it in with npm (i.e. npm build tool looks for both npm and pnpm files)? Since far as I can see from a quick glance for purposes of this its more or less same as npm except for the command/lock file, so I feel like an extra class would be a lot of repeat code that would be a pain to manage in future

If they are mostly equivalent, we can add it to the npm section. But please add a comment to explain this decision and document any differences if you notice any.