In [1] and [2], Git LFS learned how to run its tests under prove(1) and
replaced many of its script/*'s with Makefile-based targets.

The platform-specific instructions for building `*.deb`'s and `*.rpm`'s
must update accordingly so as not to refer to outdated (and now broken
invocations) such as script/test. For example, this particular
invocation--script/test--should be replaced with 'make test' instead.

Apply the necessary changes to avoid bitrot and keep the Git LFS
script/target invocations up-to-date.

[1]: git-lfs/git-lfs#3125
[2]: git-lfs/git-lfs#3144

In commit c4874df of PR git-lfs#971 the
script/cibuild script was revised to run the Go test suite just for our
"git" Go package in order to confirm that we do not leak the GIT_TRACE
environment variable to Git itself when it is set.

Later, in commit 2235198 of PR git-lfs#3144,
our Makefile was updated to start by running some Git commands
("git describe" and "git rev-parse") to determine the current tagged
version of the project.

When GIT_TRACE=1 is set in second run of the Go test suite, these initial
Git command output Git trace log lines, which does not affect the
validity of the second Go test of our "git" package but does add some
noise to the output of the script/cibuild script.  We therefore just
unset the GIT_TRACE environment variable for these two Git commands in
our Makefile.

In PR git-lfs#4903 we removed use of a "vendor" directory for Go modules,
so we can now drop several references to that directory from our
CI build script and Makefile, and our license documentation.

Note that the "lint" Makefile target was introduced in PR git-lfs#3144
(and then modified in PR git-lfs#3208 when the project adopted Go modules),
and existed to check whether all dependencies outside those from
the Go standard library existed in the "vendor" directory.  At
present, though, the command now finds no dependencies that are
neither in the standard library nor are Go modules, and so is a
no-op which we can simply remove.

In commit 4c422b4 of PR git-lfs#113 the
script/release script was added, which runs the script/release.go program,
which uploaded release binaries to GitHub via a POST request, based on the
values in a bin/releases/build_matrix.json file.  This file is no longer
created because the script/build.go file and accompanying script/bootstrap
script were removed in commit 2235198 of
PR git-lfs#3144.

As we do not use the script/release or script/release.go files anymore
as part of our release process, we can delete them now.

In commit 4c422b4 of PR git-lfs#113 the
script/release script was added, which runs the script/release.go program
to upload release binaries to GitHub via a POST request based on the
values in a bin/releases/build_matrix.json file.  This file is no longer
created because the script/build.go file and accompanying script/bootstrap
script were removed in commit 2235198 of
PR git-lfs#3144.

As we do not use the script/release or script/release.go files anymore
as part of our release process, we can delete them now.

In commit 4c422b4 of PR git-lfs#113 the
script/release script was added, which builds and runs a Go program
from the script/script.go and script/release.go files.  The mainRelease()
function in that program uploads release binaries to GitHub via a POST
request based on the values in a bin/releases/build_matrix.json file.

However, that JSON file is no longer created because the script/build.go
file and accompanying script/bootstrap script were removed in commit
2235198 of PR git-lfs#3144.

As we do not use the script/release or remaining script/*.go files anymore
as part of our release process, we can delete them now.

In commit 4c422b4 of PR git-lfs#113 the
script/release script was added, which builds and runs a Go program
from the script/script.go and script/release.go files.  The mainRelease()
function in that program uploads release binaries to GitHub via a POST
request based on the values in a bin/releases/build_matrix.json file.

However, that JSON file is no longer created because the script/build.go
file and accompanying script/bootstrap script were removed in commit
2235198 of PR git-lfs#3144.

As we do not use the script/release or remaining script/*.go files anymore
as part of our release process, we can delete them now.

Since commit 9b0adeb of PR git-lfs#3125,
when we converted our test suite to use the "prove" command, we have
run up to nine test jobs in parallel in our primary test builds.

However, as of commit 7fd5aa6 in
PR git-lfs#3144, we only use a maximum of four parallel test jobs when
building our Linux RPM packages.  This has the effect of slowing
down our CI suite, because, ever since commit
212c051 in PR git-lfs#3932, we build a
range of Linux packages in our GitHub Actions CI workflow.

(Note that for historical reasons, we only run the full "make test"
Makefile target in our "t" test directory  when building RPM packages;
in our Debian packages, we just run the Go language tests.  While this
discrepency is worth addressing, for the moment we simply aim to
improve the runtime of our RPM package builds.)

Since commit 9b0adeb of PR git-lfs#3125,
when we converted our test suite to use the "prove" command, we have
run up to nine test jobs in parallel in our primary test builds.

However, as of commit 7fd5aa6 in
PR git-lfs#3144, we only use a maximum of four parallel test jobs when
building our Linux RPM packages.  This has the effect of slowing
down our CI suite, because, ever since commit
212c051 in PR git-lfs#3932, we build a
range of Linux packages in our GitHub Actions CI workflow.

(Note that for historical reasons, we only run the full "make test"
Makefile target in our "t" test directory  when building RPM packages;
in our Debian packages, we just run the Go language tests.  While this
discrepency is worth addressing, for the moment we simply aim to
improve the runtime of our RPM package builds.)

Since commit 9b0adeb of PR git-lfs#3125,
when we converted our test suite to use the "prove" command, we have
run up to nine test jobs in parallel in our primary test builds.

However, as of commit 7fd5aa6 in
PR git-lfs#3144, we only use a maximum of four parallel test jobs when
building our Linux RPM packages.  This has the effect of slowing
down our CI suite, because, ever since commit
212c051 in PR git-lfs#3932, we build a
range of Linux packages in our GitHub Actions CI workflow.

(Note that for historical reasons, we only run the full "make test"
Makefile target in our "t" test directory  when building RPM packages;
in our Debian packages, we just run the Go language tests.  While this
discrepency is worth addressing, for the moment we simply aim to
improve the runtime of our RPM package builds.)

Since commit 9b0adeb of PR git-lfs#3125,
when we converted our test suite to use the "prove" command, we have
run up to nine test jobs in parallel in our primary test builds.

However, as of commit 7fd5aa6 in
PR git-lfs#3144, we only use a maximum of four parallel test jobs when
building our Linux RPM packages.  This has the effect of slightly
slowing down our CI suite, because, ever since commit
212c051 in PR git-lfs#3932, we build a
range of Linux packages in our GitHub Actions CI workflow.

(Note that for historical reasons, we only run the full "make test"
Makefile target in our "t" test directory when building RPM packages;
in our Debian packages, we just run the Go language tests.  While this
discrepancy is worth addressing, for the moment we simply aim to
improve the runtime of our RPM package builds.)