fix: Avoid asking questions about updated files

[adskyiproger]

Description

See issue here: https://github.com/opencrvs/opencrvs-farajaland/actions/runs/15561736743/job/43815567582

What Do These Options Do?

• --force-confold: Keeps the currently installed version of any configuration file (the "old" one).
• --force-confdef: If the config file was not changed, automatically installs the new version; otherwise, keeps your changes unless you specify otherwise.

ansible.builtin.package doesn't have an option to take non-interactive decision: https://docs.ansible.com/ansible/latest/collections/ansible/builtin/package_module.html

Provision script was tested multiple time after fix at: https://github.com/opencrvs/opencrvs-farajaland/pull/1452/files

PR also contains a fix for: https://github.com/opencrvs/opencrvs-farajaland/actions/runs/15585106472/job/43889489796

Test results are here: https://github.com/opencrvs/opencrvs-farajaland/actions/runs/15587006343

Checklist

• I have linked the correct Github issue under "Development"
• I have tested the changes locally, and written appropriate tests
• I have tested beyond the happy path (e.g. edge cases, failure paths)
• I have updated the changelog with this change (if applicable)
• I have updated the GitHub issue status accordingly

[github-actions]

Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:

• Changelog is read by country implementors who might not always be familiar with all technical details of OpenCRVS. Keep language high-level, user friendly and avoid technical references to internals.
• Answer "What's new?", "Why was the change made?" and "Why should I care?" for each change.
• If it's a breaking change, include a migration guide answering "What do I need to do to upgrade?".