feat!: add conflict resolution option to configuration file

[gahyusuh]

What was the problem/requirement? (What/Why)

We need to provide a way for users to set their preferences for how file conflicts are resolved during downloads (when downloading files with the same file path or filename that already exist on the local.)

What was the solution? (How)

• Added a new conflict_resolution setting to the configuration file.
• Provided a dropdown in the Configuration GUI where users can select their preferred conflict resolution option.
• Ensured that the --conflict-resolution option can still be specified in the download-output CLI command, which will override the config setting if both are present.

What is the impact of this change?

Users can now set their preferred method for resolving file conflicts directly in the configuration file, providing a more streamlined user experience.

How was this change tested?

• hatch run lint && hatch run test
• Configuration GUI testing: verified that the selected conflict resolution option is accurately saved in the config file.
• CLI testing: Checked the behaviour when downloading output with file conflicts. Specifically, tested the combination of auto-accept and conflict-resolution.
  • auto-accept True, and conflict-resolution NOT_SELECTED --> No user prompt, executes default behaviour - CREATE_COPY
  • auto-accept True, and conflict-resolution something selected --> No user prompt, executes selected resolution
  • auto-accept False, and conflict-resolution NOT_SELECTED --> No user prompt, executes selected resolution
  • auto-accept False, and conflict-resolution something selected --> User is prompted for resolution, executes selected option
• Priority testing: Verified that CLI-specified conflict resolution takes precedence over the config file setting.

Was this change documented?

No.

Is this a breaking change?

No.