Since we're about to do a v3.0.0 release, let's bump the version to v3.
Make this change automatically with the following command to avoid any
missed items:
git grep -l github.com/git-lfs/git-lfs/v2 | \
xargs sed -i -e 's!github.com/git-lfs/git-lfs/v2!github.com/git-lfs/git-lfs/v3!g'
When our go.mod file was introduced in commit
114e85c2002091eb415040923d872f8e4a4bc636 in PR #3208, the module
path chosen did not include a trailing /v2 component. However,
the Go modules specification now advises that module paths must
have a "major version suffix" which matches the release version.
We therefore add a /v2 suffix to our module path and all its
instances in import paths.
See also https://golang.org/ref/mod#major-version-suffixes for
details regarding the Go module system's major version suffix rule.
There are several cases in which we can pass in Unix-style paths in the
Git Bash environment, which is MINGW64-based, including in file URLs. To
make such paths work, let's accept such URLs with the Unix-style paths
and then translate them to Windows-style paths automatically. Note that
passing Windows-style paths to "cygpath -W", which is what we use in
this case, works fine, so there's no regression in the Git Bash case.
