Change: method write and read settings.yml #1441

[Ludy87]

Description

Please provide a summary of the changes, including relevant motivation and context.

Closes #1441

Checklist:

• I have read the Contribution Guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings

Contributor License Agreement

By submitting this pull request, I acknowledge and agree that my contributions will be included in Stirling-PDF and that they can be relicensed in the future under the MPL 2.0 (Mozilla Public License Version 2.0) license.

(This does not change the general open-source nature of Stirling-PDF, simply moving from one license to another license)

[Frooodle]

Is this a breaking change for old settings files?

[Ludy87]

Is this a breaking change for old settings files?

The process is:

1. the "old" settings.yml is read in
2. the template is read in
3. the settings in the settings.yml are compared with the template, if there are differences, the value is left in the settings.yml
4. if a new key is added to the template, it is also added to the settings.yml
5. if a key has been removed from the template, it is removed from the settings.yml

[Frooodle]

Awesome stuff!

[sonarqubecloud]

Quality Gate failed

Failed conditions
1 Security Hotspot

See analysis details on SonarCloud