Related Issue

Closes #516
Supersedes #519

Description

#516 was a regression split across two PRs so it was a little tough to catch, as well as the behavior of teststep.Config is not obvious:

• Add additional import test modes #442
  • Removed teststep.Config usage in favor of a string, however, the original mergedConfig is actually ignored when creating a new teststep.Config, which is confusing, but would essentially result in a ConfigFile/Directory test step being shaved down into just a string that has a required_providers block.
• plannable import: support step.ConfigExact = [true|false] for all config sources #494
  • Removed the check for reusing a prior test step config, because it was checking a value that was always populated (either with real config via step.Config or just a shaved down required_providers block via step.ConfigFile/Directory)

This PR reintroduces the usage of a teststep.Config over a raw string, adjusts some of the existing tests to cover this scenario, and adds a new one for the command import mode.

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

No