Describe the bug
When using rpm packages and packages in general there is an option to define config files which will be saved on removal and will not be installed on an upgrade.
Currently the config files under /etc/defguard are re-installed ie overridden on an upgrade compared to being saved and the new default config will be installed as let say /etc/defguard/core.conf.rpmnew

To Reproduce
Steps to reproduce the behavior:

1. install let say v 1.5.1 with the rpm package
2. change somethings in /etc/defguard/core.conf
3. upgrade to let say 1.5.2 using the rpm pacakge
4. see that the content of the config file was replaced by the defaults

Expected behavior
The config file will not be changed and a new file with extention .rpmnew will be created.

Version information

• Defguard Core version: v1.5.1+

Additional context
I am trying to install a full deployment in a lab to verify that I can re-create the setup in production.