textproc/jq: Use tarball published by upstream

[jrm]

Summary

This also fixes an issue with jq --version not reporting the version.
While here, also pet portclippy/portfmt/portlint.

Reported by: Vedran Miletic <[e-mail]>
Sponsored by: The FreeBSD Foundation

[michaelo]

If so, the project has moved: https://github.com/jqlang/jq

[jrm]

Use new upstream site rather than relying on forwarding

[michaelo]

I wonder why this port not uses "USE_GITHUB": https://docs.freebsd.org/en/books/porters-handbook/makefiles/#makefile-master_sites-github

[jrm]

In D42758#975365, @michaelo wrote:

I wonder why this port not uses "USE_GITHUB": https://docs.freebsd.org/en/books/porters-handbook/makefiles/#makefile-master_sites-github

It was using USE_GITHUB, but I switched it to fix the issue with jq --version and also because of the warning at the top of that page you just shared.

[michaelo]

In D42758#975376, @jrm wrote:

In D42758#975365, @michaelo wrote:

I wonder why this port not uses "USE_GITHUB": https://docs.freebsd.org/en/books/porters-handbook/makefiles/#makefile-master_sites-github

It was using USE_GITHUB, but I switched it to fix the issue with jq --version and also because of the warning at the top of that page you just shared.

Indeed, then we have a ports framework issue. Different discussion.

[diizzy]

In D42758#975365, @michaelo wrote:

I wonder why this port not uses "USE_GITHUB": https://docs.freebsd.org/en/books/porters-handbook/makefiles/#makefile-master_sites-github

That's a "last resort" solution, use release tarballs/archives whenever possible.

Usually when version information is missing it's because upstream's framework relies on Git to figure out what version is being built (this is usually adjusted in release archives in one way or another) and Git is usually not called in the correct path anyway so it fails or reports incorrectly.
In this case it seems like this script is being used to determine version: https://github.com/jqlang/jq/blob/master/scripts/version and since we don't download .git it fails.

This isn't a framework bug rather a limitation of upstream's build script but since upstream now (as of 1.4) ships release tarballs which handles this issue there's nothing to fix.