Fixes #2761 change transport direction

[msevestre]

Fixes #2761

Description

Probem was that it was seen as a non structural change (e.g. changing the expression profile structure). now I am also checking that all used expression profile have the same structure version

Type of change

Please mark relevant options with an x in the brackets.

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires documentation changes (link at least one documentation issue):
• [ ] Algorithm update - updates algorithm documentation/questions/answers etc.
• [ ] Other (please describe):

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [ ] Integration tests
• [x] Unit tests
• [ ] Manual tests
• [ ] No tests required

Reviewer checklist

Mark everything that needs to be checked before merging the PR.

• [ ] Check if the code is well documented
• [ ] Check if the behavior is what is expected
• [ ] Check if the code is well tested
• [ ] Check if the code is readable and well formatted
• [ ] Additional checks (document below if any)
• [ ] Check if documentation update issue(s) are created if the option This change requires a documentation update above is selected

Screenshots (if appropriate):

Questions (if appropriate):

[Yuri05]

If we use a PR template, we should also tick some options when creating a PR 😉

[msevestre]

Agreed. I forgot to check. Still have to get used to doing this here