Currently, it is not possible to obtain the source location of a runtime
error making it difficult sometimes to identify the cause of an issue.
If an AST node ID is available, the source location can be obtained, so
add this information to runtime errors.

ref.Val values returned by the following types are examined for error
state and if an error and no AST node has been set, the node ID of the
Interpretable is added to the error.

* evalAnd
* evalAttr
* evalBinary
* evalExhaustiveConditional
* evalList
* evalMap
* evalMap
* evalObj
* evalOr
* evalTestOnly
* evalUnary
* evalVarArgs
* evalWatchAttrQual
* evalWatchConstQual
* evalWatchQual
* evalZeroArity

Filter and map macros previously reused Expr.id values for repeated
references to the accumulator var. After this change, the parser
should always provide unique node IDs per AST assuming standard macros.

* Set membership test rewriting optimizer
* Additional tests for macros and enums

%s is defined to support "all numerical types (int, uint, and double)."
but later the docs also say:
"Passing an incorrect type (an integer to `%s`) is considered an error"

The example in the parenthetical contradicts the definition of %s.

This change replaces the parenthetical example with one that is
accurate and verified by an existing test case. This change also adds
an explicit test case to verify that it is valid to pass an in to %s.

Adds a repl option to include packages of linked in message types.
This allows using the types without preparing a hermetic set of
descriptors to load from file.

)

Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.2 to 1.15.4.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](follow-redirects/follow-redirects@v1.15.2...v1.15.4)

---
updated-dependencies:
- dependency-name: follow-redirects
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>