GitHub actions workflows

[stellaprins]

• Split SBMLShowcase/.github/workflows/non-omv.yml in two to separate docker / biosimulators related workflows (see below) to differentiate between biosimulators issues and issues with our code.

    - name: Test omex file creation
      run: |
        pip install "pymetadata>=0.4.2" docker "requests<2.32.0"
        cd SBML/tests    
        python ./test_biosimulators_docker.py

    - name: Test biosimulators compatibility table creation
      run: |
        cd SBML/tests
        sudo rm -rf output
        python ./test_compatibility_biosimulators.py --output-dir=tmp_plots

• Ammend Test omex file creation workflow: for /test_biosimulators_docker.py add command line option for running it on biosimulators or not. Add one workflow (which runs the omex file on biosimulators) to the docker / biosimulators related workflows file, and one (which does not run the omex file on biosimulators) to the workflows file that does not involve docker or biosimulators.

[stellaprins]

• non-omv-remote.yml to include any code that relies on the biosimulators website (run_biosimulators_remotely)

• non-omv-docker.yml to include any code that relies on docker containers (run_biosimulators_locally)

• non-omv.yml add create_combined_results_table with dummy results_remote and results_local tables.

• check whether all components of non-omv.yml are used. e.g.

- name: Run tests
      run: |
        omv install jneuroml

[stellaprins]

Testing changes to the github actions workflows without having to commit and push the changes to the remote repository

• installed act to run github actions locally
• @pgleeson suggested to edit workflow files on the github webbrowser or making a fresh and private repository dedicated to testing workflows

[stellaprins]

Right now dummy data has been used but using data from the triggering workflow could be implemented down the line to use results (for example the remote and local results that are generated in separate workflows and combined into one table in yet another workflow) from a triggering workflow.