fix: getStandardKcat with multiple subSystems

[edkerk]

Main improvements in this PR:

• fix:
  • getStandardKcat handling models that have multiple subSystems assigned to the same reaction.

I hereby confirm that I have:

• Selected develop as a target branch (top left drop-down menu)

[github-actions]

This PR has been automatically tested with GH Actions. Here is the output of the tests:

 
Running geckoCoreFunctionTests
Model-specific DLKcat input stored at /home/m/actions-runner/_work/GECKO/GECKO/test/unit_tests/ecTestGEM/data/DLKcat_input_test.tsv
Limit has been reached. Protein P5 seems to be problematic. Consider changing the kcat.
Done geckoCoreFunctionTests
__________

Note: In the case of multiple test runs, this post will be edited.

[mihai-sysbio]

The output of the action looks unexpected, but also doesn't seem to be caused by changes in this PR. Should it be investigated further (perhaps as a separate issue)?

Model-specific DLKcat input stored at /home/m/actions-runner/_work/GECKO/GECKO/test/unit_tests/ecTestGEM/data/DLKcat_input_test.tsv
Limit has been reached. Protein P5 seems to be problematic. Consider changing the kcat.

[ae-tafur]

The output of the action looks unexpected, but also doesn't seem to be caused by changes in this PR. Should it be investigated further (perhaps as a separate issue)?

Model-specific DLKcat input stored at /home/m/actions-runner/_work/GECKO/GECKO/test/unit_tests/ecTestGEM/data/DLKcat_input_test.tsv
Limit has been reached. Protein P5 seems to be problematic. Consider changing the kcat.

I think is ok, this is output from the functions tested. runDLKcat (not 100% sure), and flexibilizeProtConcs (when a limit is set)

[mihai-sysbio]

Other recent PRs have a much more verbose output when running the test suite, e.g. #295 (comment) . Perhaps I missed something, but I was expecting a similar output here.

[ae-tafur]

Other recent PRs have a much more verbose output when running the test suite, e.g. #295 (comment) . Perhaps I missed something, but I was expecting a similar output here.

Yeap, that was because a test was failing (check more here), but due to RAVEN reversibility assignment. This was fixed here