Cloning an existing repo with Configure overwrites settings from file

[isc-pbarton]

resolves #819

If the cloned repo has a settings file, its values will overwrite those chosen earlier in the Configure prompts. I agree with the requestor that this is always desired behavior.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.77%. Comparing base (aef7832) to head (310ce67).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #860   +/-   ##
=======================================
  Coverage   49.77%   49.77%           
=======================================
  Files          24       24           
  Lines        3281     3281           
=======================================
  Hits         1633     1633           
  Misses       1648     1648           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[isc-pbarton]

Includes changes from #859 as well because I did not feel like resolving a merge conflict later.

[isc-dchui]

Just a quick question.

[isc-dchui]

So this PR also contains the changes for #859. Is that intentionally to avoid a merge conflict later? If so, will the git history correctly reflect that these changes are not actually from this PR?

[isc-dchui]

Oh wait sorry didn't see your earlier comment

[isc-pbarton]

@isc-dchui Yep, that was intentional to avoid merge conflict on the changelog. The history should be all good now - I merged #859 and changed the base on this repo to force GitHub to refresh its data associating commits to PRs.