sort hash keys to generate a stable result

using unsorted hash keys technically provides the same result, but
the testcases are unable to validate the generated output
integrate.t: test all components except hardware-dependent ones

Use the files generated by 'setup-storage2 -X -d -f <filename>' and
replay a complete run (from parsing the configuration to creating
the actual command list and fstab/crypttab/disk_var.sh content)

This test intercepts setup-storage's state variables at specific
stages to provide the correct input or validate the generated output.
Its role is to verify whether all parts continue to 'fit together'
even though the actual code changes during refactoring.

Add a new test configuration:

  - generate the required set of file by executing
    setup-storage2 -X -d -f <filename>
  - copy /tmp/state_<epoch>.* to t/data
  - add 'state_<epoch>' to the @testcases variable

You can rename the files as long as all files have the same filename
part ('state_<epoch>') and the extension (.state# / .id_map) is kept.