Add History Service test sequence

[surgitaix]

Discussion on PAT 21: Should it be a 1) separate test, or 2) more or less integrated with the current test sequence:

1. pro: easier to separate and clearly define the range to be requested. Also not "spammed" with Waveforms
2. pro: History Service runs in background, realistic scenario, even with multiple waveform. More integrated = no separate testing

option 2) was "felt" more in favor here. Especially since the HS currently is designed to exclude Waveforms from the HS. The Version range can be in relation to the latest observed version (e.g. a Report, or MdibResponse), e.g. X1: last full 1000st Version (i.e. 0, 1000, 2000, ect..); X2 = X1+200;

Ideas for test cases:
a. HistoryQuery with VersionRange [X1, X2] correctly answered (subtests: a.1. with Waveforms, a.2. without waveforms)
b. HistoryQuery with VersionRange [X1, X2] and HistoryicMdib correctly answered (with or without waveforms, both are accepted)
c. HistoryQuery with Timestamp range [current time -30 sec,current time -15 sec] successfully answered. (with or without waveforms, both are accepted)

Optional test cases:
d. LocalizedText Elements are corretly requestable (do not need to be accessable via HS if they are accessable via Localization Service)