Update test matrix

[syntron]

Based on PR #400 / #402 the test matrix needs to check for different settings including a breaking change in OM;

    # test for:
    # * Python 3.10 - oldest supported version
    # * Python 3.12 - changes in OMCSession / OMCPath
    # * Python 3.14 - latest Python version
    python-version: ['3.10', '3.12', '3.14']
    # * Linux using ubuntu-latest
    # * Windows using windows-latest
    os: ['ubuntu-latest', 'windows-latest']
    # * OM 1.25.0 - before changing definition of simulation overrides
    # * OM stable - latest stable version
    # * OM nightly - latest nightly build
    omc-version: ['1.25.0', 'stable', 'nightly']
    # => total of 12 runs for each test

[adeas31]

We really don't want to test a specific OM version.

[syntron]

Do we? I can remove it; however, at this point we have a hard to find break due to the handling of the simulation related options. My idea was to check / verify this for a given time. Please also see the comment by @joewa about the use of older versions (#401 (comment))

[adeas31]

OM releases around 2 versions every year, if we start testing specific versions then it will be too much.
The fixes done in PR #400 and #402 are backwards compatible so even if @joewa is using OM 1.25.5 it will still work.

[syntron]

OK; I scaled it down to 2x Python; 2x OS; 2x OM - the minimum number to test

[adeas31]

It will be 18 tests in total.

[syntron]

fixed!

[adeas31]

18 runs for each test.

This is additional information that will quickly become outdated once a new Python version is added. I suggest not including this line, as it is easy to forget updating this part when other parts of the file are modified.

[syntron]

quite right! - I did remove the line ...