fix: clear config before each run

[pkey]

Pull Request Submission Checklist

• [x] Follows CONTRIBUTING guidelines
• [x] Commit messages are release-note ready, emphasizing what was changed, not how.
• [x] Includes detailed description of changes
• [x] Contains risk assessment (Low | Medium | High)
• [x] Highlights breaking API changes (if applicable)
• [x] Links to automated tests covering new functionality
• [x] Includes manual testing instructions (if necessary)
• [x] Updates relevant GitBook documentation (PR link: ___)
• [x] Includes product update to be announced in the next stable release notes

What does this PR do?

It's common that there are left over values from local testing. This can be confusing and takes time to figure out. This change does the cleaning every time. I noticed a couple of instances on #ask-cli where folks tripped over this.

Where should the reviewer start?

How should this be manually tested?

npm run test

What's the product update that needs to be communicated to CLI users?

No update.

[github-actions[bot]]

	Warnings
:warning:	There are multiple commits on your branch, please squash them locally before merging!

Generated by :no_entry_sign: dangerJS against f1509151527298bcffa5258042b161d316fb3424