Duplicate files overwrite behaviour

[BenWinchester]

Currently, if CLOVER is re-run, many of the auto-generated files are deleted. This behaviour would be altered via

• The introduction of a --regenerate-profiles or --regenerate flag which, when specified, causes profiles to be regenerated. If the flag isn't specified,
  • Existing profiles are used if they exist,
  • New profiles are generated if there are no existing profiles to use;
• If a profile is regenerated, the old profile is renamed with a ".1" suffix. This cycling would happen indefinitely, with profiles being given successively higher suffix numbers. E.G., if profiles are numbered “.1”, “.2”, and “.4”, the old profile which is moved upon the regeneration of the profiles is given the suffix “.5”.

[BenWinchester]

On this, if CLOVER is run in such a way that the profiles would be regenerated, the options are:

• Pause the operation and ask for a y/n confirmation from the user;
• Warn the user that their profiles will be regenerated, renaming the old files where appropriate, and continuing with the flow.