User scenarios test for real storage

[grusev]

Reference Issues/PRs

What does this implement or fix?

This is initial PR for proof of concept tests for end user scenario testing. The end user scenario testing stress on using arcticdb as a storage platform which handles database operations needed to fulfil certain need. The tests there put arctic db on continious exposure of different types of load, including errorneous. The stress is over correct operation no matter what data is given for certain time or sequence of events

UtilizationProfile - a way to have configurable profile for different types of storages / loads.

AppendGenerator - provides sequence of dataframes to be appended one after another
UpdateGenerator - provides sequence of dataframes to update single dataframe
ErrorDataGenerator (basic implementation) - provides sequence of dataframes that should produce errors if attempted to be written to arctic

There are thre simple test cases undrlying the concept of putting each storage to a series of tests, that simulate possible user actions. The appends/updates/errors(in future deletion etc ) can be in any orger this would put any arcticdb storage we support to a test if all operations can be done without a problem in any sequence of events.

Any other comments?

Checklist

Checklist for code changes...

• Have you updated the relevant docstrings, documentation and copyright notice?
• Is this contribution tested against all ArcticDB's features?
• Do all exceptions introduced raise appropriate error messages?
• Are API changes highlighted in the PR description?
• Is the PR labelled as enhancement or bug so it appears in autogenerated release notes?