DSC should pass the `name` field to resource invocations as metadata

Summary of the new feature / enhancement

As a DSC resource author, I want to be able to provide trace messages with as much usable context to consumers as possible, including the specific resource instance that is being invoked.

Currently, resources don't have access to the name field from a resource instance in a configuration document, so readers of the resource trace messages may not understand which resource instance emitted those messages.

Proposed technical implementation details (optional)

Standardize passing the name field to DSC resources when using dsc config commands as part of the _metadata struct.

Resource authors would have to implement their resources to include the instance name if passed through metadata. For direct invocations with dsc resource commands, the resources shouldn't expect to receive a name for the instance.

Start by tracing the dsc config command path into resource invocations and locate the _metadata structure or equivalent. Done means configuration-based resource invocations receive the resource instance's name as metadata, while direct dsc resource invocations do not expect one; add or update coverage where the existing invocation behavior is tested.