Only single latest migration can be applied

Looks like I forgot to test one usecase for !4 (merged) 🙁

In order to reproduce, create a new *.silecsdesign (from some Fesa class) and replaced the xml of it with the 0.10.0 migration test example.

My expectation was, that all availabe migration scripts, up to the currently installed version should be executed:

• 0_10_0 --> 1_0_0
• 1_0_X --> 2_0_0
• 2_0_X --> 2_1_X
• 2_1_X --> Current Version (no dedicated migration script)

But the migration tool only checked for a migration script 0.10.0 to 5.6.7, which ofc does not exist. Here the console log:

[schwinn@asl754 silecs-cli]$ ./silecs -m ~/workspace-acc8/SilecsTest123 5.6.7
using sileces base path: /home/bel/schwinn/lnx/tmp/silecstest/5.6.7
Using fesa version: 7.4.0
No available fesa codegen version for version 7.4.0. Searching for different version
Using codegen version 7.3.0
No module named '0_10_xto5_6_x'
There is no Migration Script for an update from: 0.10.0 to 5.6.7
Using generic migration-script. Only basic xml-version strings will be changed.

INFO: Migration 0.10.0 --> 5.6.7 
Parsing file: '/home/bel/schwinn/lnx/workspace-acc8/SilecsTest123/src/SilecsTest123.silecsdesign'
Info: Replaced old silecs-versiong string: 0.10.0 with: 5.6.7
Info: Replaced old silecs-xmlSchema
File '/home/bel/schwinn/lnx/workspace-acc8/SilecsTest123/src/SilecsTest123.silecsdesign' successfully migrated

(Tested with !8 (merged) applied)