Feature/benchmark test for multiple input flows

[ciaradunks]

Changes proposed in this pull request:

• Create benchmark test for multiple input flows of an asset
• Create benchmark test for multiple output flows of an asset

The following steps were realized, as well (if applies):

• [ ] Use in-line comments to explain your code
• [ ] Write docstrings to your code (example docstring)
• [ ] For new functionalities: Explain in readthedocs
• [ ] Write test(s) for your new patch of code (pytests, assertion debug messages)
• [ ] Update the CHANGELOG.md
• [ ] Apply black (black . --exclude docs/)
• [ ] Check if benchmark tests pass locally (EXECUTE_TESTS_ON=master pytest)

Please mark above checkboxes as following:

• [ ] Open
• [x] Done

:x: Check not applicable to this PR

_{For more information on how to contribute check the CONTRIBUTING.md.}

[smartie2076]

I think that you, by mistake, added the input files for this tests already in this commit (8890878c941c9cc7f0597d04a74095052b3f2309), and merged it to dev

[smartie2076]

@ciaradunks can you push your updates on the input files prepared for this test? Then we can merge and close the PR.

Remove Fix #507 and #802 in your first post, so that the issues are not automatically closed when the PR is merged.

[ciaradunks]

@smartie2076 I didn't have time in the end to make conclusive inputs, I only got to the point where I was testing out different ways of defining inputs as a list and what may/may not work. So I think this can simply be closed and the issue will be opened again in the future. I have still removed Fix #507 and #802 though.