Fix plugin tracing again 😭

[carolynvs]

What does this change

When we fixed recursive plugin loading in #2071, we did so by disabling config loading in the plugin. This was almost right but not quite. While Porter does resolve the relevant config for the plugin and pass it on stdin, this does not provide some of the general configuration settings that can be used by the plugin such as logging and telemetry.

Specifically, our change caused a regression where the plugins didn't load the telemetry configuration and stopped sending trace data.

I have updated how configuration data is loaded for plugins:

1. When we start a plugin binary we grab relevant configuration settings and pass them as environment variables to the plugin.
2. When loading configuration for a plugin, we skip reading just the config file, but we still load configuration using environment values.
3. Added a new telemetry setting that redirects traces from the standard open telemetry collector to write them to a file instead (in PORTER_HOME/traces). This helped me finally write a regression test for sending trace data so that I don't accidentally break this again.

While I was working on this I found that we aren't handling close errors when we close porter's log file and we were missing a race condition where the plugin closes the log file before porter is done with it. I've split up the log and trace files for the plugins and porter so that they write to CORRELLATIONID.json for porter and
CORRELLATIONID-PLUGINKEY.json for the plugins.

What issue does it fix

Restores plugin telemetry.

Closes #2057

Notes for the reviewer

Checklist

• Did you write tests?
• Did you write documentation?
• Did you change porter.yaml or a storage document record? Update the corresponding schema file.
• If this is your first pull request, please add your name to the bottom of our Contributors list. Thank you for making Porter better! 🙇‍♀️

Reviewer Checklist

• Comment with /azp run test-porter-release if a magefile or build script was modified
• Comment with /azp run porter-integration if it's a non-trivial PR

[vdice]

Thanks for the context and breakdown of changes. LGTM!