Puppet Agent Reads Environment From Wrong Location

As of version 7.10, puppet agent will read its environment out of `last_run_summary.yaml` instead of using what has been specified in `puppet.conf` if there has been any sort of error with the environment specified in `puppet.conf` or if the environment was changed based on something server-specified or ENC specified (like when a customer manually moves a node into a canary environment). This is problematic for anyone who is trying to manage the environment from the agent specifically and not anywhere else. `puppet.conf` should be a higher priority than a variable that was written in a summary report that users are not expected to modify. Restarting the agent has no impact on the behavior and will continue to use the environment from the summary report indefinitely.