[Bug]: the working directory shouldn't be used to resolve the last tag when a bespoke tag format is provided

[purpleclay]

What happened?

nsv has support for defining a custom tag format, especially useful when working within a mono repo, or a Go project with multiple binaries. For example:

kubernetes\
  kubectl\     <<-- --format "kubectl/{{.Version}}"
  kubeadm\     <<-- --format "kubeadm/{{.Version}}" 

When looking at the output from nsv it is using the working directory to scan for logs and to resolve the latest tag, which causes two problems:

1. Each individual binary tag version can end up being locked together.
2. If the tag format doesn't match the working directory, resolution can fail all together.

Steps to reproduce it

...

Which version?

v0.12.1

Which operating system(s) are you using?

All

Code of Conduct

• I agree to follow this project's Code of Conduct