Describe the bug
jq has the somewhat surprising behavior of recognizing additional options after a non-option argument has been encountered. While I won't suggest changing that behavior (due to compatibility concerns), it would be nice if jq at least recognized -- as an indication to stop attempting to parse options. This is a pretty commonly-implemented feature of commandline tools.

Given that it's currently an error to pass -- in a context where options are recognized, I don't think it would introduce a compatibility issue.

To Reproduce
Expected to remain the same:

$ jq --null-input --args '$ARGS' foo bar baz --zorch
jq: Unknown option --zorch
Use jq --help for help with command-line options,
or see the jq manpage, or online docs  at https://jqlang.github.io/jq

Current behavior of --:

$ jq --null-input --args -- '$ARGS' foo bar baz --zorch
jq - commandline JSON processor [version 1.7]

Usage:	jq [options] <jq filter> [file...]
...

Expected behavior
Suggested behavior of --:

$ jq --null-input --args -- '$ARGS' foo bar baz --zorch
{
  "positional": [
    "foo",
    "bar",
    "baz",
    "--zorch"
  ],
  "named": {}
}

Environment (please complete the following information):

• OS and Version: N/A (FWIW I use macOS and various Linuxes)
• jq version: 1.7

Additional context
N/A