Backport Smode Beta configurations to a Stable Smode version

If you just finish a Smode Tech Beta program accompaniment and you want to switch to a new stable release that embed all validated code fixes, to benefit from long term support, you will loose your current Beta configuration of Smode preferences panel settings

Indeed, Smode never load configuration of a futur version of Smode
Smode Beta version are always and wrongly considered as futur version of Smode Stable

This is due to the fact that a Beta version of Smode have several patch for each fix progress (code changes);
Against a Stable version of Smode only have one unique Patch increment for several validated fix batch.
For instance 100 code fixes progression will be released in stable Patch Batch number 4, on top of previous stable Patch batch number 3

For instance in R13, the beta version R13.100 will be followed by a new stable version R13.4
Previously to Smode R13, Smode 10.x versions have 3 numbers instead of 2, the last number is always the Patch number.
So for instance in Smode 10.2, beta version 10.2.100 will be followed by a new stable version 10.2.4

To workaround this you have two choices:

1. Discard your beta configuration:
   This by doing nothing or to avoid surprises during next beta testing, by deleting all file named *_13_100.configuration from the folder
   %AppData%\Roaming\Smode <EditionName>\configurations
   Next Smode R13.4 will automatically port Smode R13.3 configuration files (or previous one if not present) at first boot

2. Keep your Beta configuration in new Stable Smode version:
   Before Smode R13.4 first boot, manually rename all *_13_100.configuration into *_13_4.configuration from the folder
   %AppData%\Roaming\Smode <EditionName>\configurations