Alisdair's fixes.
Co-Authored-By: Alisdair McDiarmid <alisdair@users.noreply.github.com>

Co-Authored-By: Alisdair McDiarmid <alisdair@users.noreply.github.com>

They don't seem to be present on `localhost`

command/fmt: Include source snippets in errors

command/format: Fix multi-line diagnostic output

Previously, if a diagnostic context spanned multiple lines, any lines
which did not overlap with the highlight range would be displayed as
blank. This commit fixes the bug.

The problem was caused by the unconditional use of `PartitionAround` to
split the line into before/highlighted/after ranges. When two ranges
don't overlap, this method returns empty ranges, which results in a
blank line. Instead, we first check if the ranges do overlap, and if not
we print the entire line from the context.

Previously, diagnostic errors would display the filename and line
number, along with "(source code not available)". This is because the
fmt command directly loads and parses the configuration, instead of
using the config loader.

This commit registers the manually parsed source as a synthetic
configuration file, so that the diagnostic formatter can look up the
source for the range with the error and display it.

Update ModuleCallOutput and add AbsModuleCallOutput

Module Expansion Activate!

This name method won't be called in the full graph, and remove it to
prevent confusion with the parent node in logs.

eval nodes no longer always have a context path

simplify the test a bit and add a few more combinations to the config

The expand logic was separated into
nodeExpandRefreshableManagedResource, but the orphan logic wasn't
updated.

Remove the shims where they aren't necessary from the Init and Close
provider nodes. This also removed some provider path checks from the
builtin eval context, which cannot be resolved since the context may not
be created with a ModuleInstance path.

We can't get module instances during transformation, so we need to
reduce the Dependencies to using `addrs.ConfigResource` for now.