Basic benchmarking structure

[fabianliebig]

Since #410 added too many lines, lets start over with a single basic structure, which includes:

• Benchmarking classes that execute a custom-defined callable which makes use of parametrizable setting input.
• Classes to Create and develop further settings, used in the callable.
• Results containing the DataFrame and relevant metadata based on the execution.
• One benchmark function to demonstrate the module's synergy.

After this PR is reviewed, I plan to create follow up PRs which may run in parallel:

• Refactoring of the classes and add a possibility to encapsulate the domain.
• Add the respective parts to persist the results in an S3 Bucket.

Please feel free to adjust or extend this list as necessary. I appreciate your feedback.

[AVHopp]

Here is the first approve :) Thank you very much for all of the work and for including all of the comments :)
Only thing I'd like to see removed is the plotting, but I'll leave that up to you and @AdrianSosic whether or not that should be in here.

[AdrianSosic]

Let's update the PR description and we are ready to go 🚀
As agreed, a follow-up PR will take care of refactoring the class responsibilities but as a first version, this will fulfill its purpose 👍🏼