Generate NOTICE.txt from deps in shipped binary

[stuartnelson3]

The original implementation, using go list -m -json all, lists dependencies that aren't actually being used in the shipped binary.

The change here lists only dependencies being shipped to the customer, then uses that information to query the full module information used by go-license-detector.

Since this is a small project I manually verified that the dependencies don't themselves have any dependencies that should be included in our NOTICE.txt.

Output of go list query:

# go list -deps -f '{{define "M"}}{{.Path}}@{{.Version}}{{end}}{{with .Module}}{{if not .Main}}{{if .Replace}}{{template "M" .Replace}}{{else}}{{template "M" .}}{{end}}{{end}}{{end}}' | sort -u
github.com/pkg/[email protected]
go.elastic.co/[email protected]
go.uber.org/[email protected]
go.uber.org/[email protected]
go.uber.org/[email protected]

This can be verified against the binary:

# go version -m ./bin/extensions/apm-lambda-extension 
./bin/extensions/apm-lambda-extension: go1.18.1
	path	command-line-arguments
	dep	elastic/apm-lambda-extension	(devel)	
	dep	github.com/pkg/errors	v0.9.1	h1:FEBLx1zS214owpjy7qsBeixbURkuhQAwrK5UwLGTwt4=
	dep	go.elastic.co/ecszap	v1.0.1	h1:mBxqEJAEXBlpi5+scXdzL7LTFGogbuxipJC0KTZicyA=
	dep	go.uber.org/atomic	v1.9.0	h1:ECmE8Bn/WFTYwEW/bpKD3M8VtR/zQVbavAoalC1PYyE=
	dep	go.uber.org/multierr	v1.8.0	h1:dg6GjLku4EH+249NNmoIciG9N/jURbDG+pFlTkhzIC8=
	dep	go.uber.org/zap	v1.21.0	h1:WefMeulhovoZ2sYXz7st6K0sLj7bBhpiFaud4r4zST8=
	build	-compiler=gc
	build	CGO_ENABLED=1
	build	CGO_CFLAGS=
	build	CGO_CPPFLAGS=
	build	CGO_CXXFLAGS=
	build	CGO_LDFLAGS=
	build	GOARCH=amd64
	build	GOOS=linux
	build	GOAMD64=v1

The -m flag causes go version to print each executable’s embedded module version information

https://go.dev/ref/mod#go-version-m

[ghost]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-06-08T06:08:28.921+0000

• Duration: 4 min 34 sec

Test stats 🧪

Test	Results
Failed	0
Passed	200
Skipped	4
Total	204

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[axw]

Looks good!