Services are restarted before the new release number is imported

[Stefal]

Describe the bug
After a 2.5.0 to 2.6.0 upgrade, and if a rtcm stream was enabled, the new release number isn't included in the rtcm stream

To Reproduce
Steps to reproduce the behavior:

1. Start with RTKBase 2.5.0
2. Upgrade to RTKBase 2.6.0
3. Connect tp the stream, and check the informations about the RTKBase release number
4. See that there is no release number

Additional context
Services are restarted (inside rtkbase_update.sh) before the new release number is imported (inside server.py)
We should merge the setting.conf and setting.conf.default inside rtkbase_update.sh