Improve handling of B10 and B09 remark 9 by 'caching' the network connection profiles on boot

[WilcodenBesten]

OCPP Version

OCPP2.0.1

Describe the problem

B09 remark 9 states: `Even when changes are made to the currently active NetworkConnectionProfile, these will not be activated until a reboot has occurred, as described in B10 - Migrate to new CSMS and B10 also required a reboot before new network connection priorities are used.

At Alfen we backported 2.0.1 network connection profiles to 1.6 to improve the migration of our customers (among other reasons). We also interpreted B10 and B09 remark 9 in a way where any change to a network connection profile will only be applied after a reboot, so we essentially 'cache' them separately. This makes the implementation more robust when running on an unstable wireless connection and more user friendly when preparing the station for migration to a new CSMS as mistakes can be caught before doing the actual migration.

Describe your solution

Only apply the change to NetworkConnectionProfile(s) after a reboot.

Additional context

No response