Installation tests

[grusev]

Reference Issues/PRs

What does this implement or fix?

This is a POC ground for creating a test suite that will be able to be executed against installable arcticdb from pypi and conda with set of tests that do now use any of our internal test fixtures that do wrap arctic in any way. On the contrary the fixtures for those tests are directly using arcticdb objects.

The tests that are selected from our test set will be sligthly modified so that they can be executed with new fixtures and old fixtures. How? instead of being tests they are modified as functions which are called from the respective test having appropriate fixture.

There is a new github workflow that will run very fast - no compilation of our project just installing python, arcticdb and all needed dependencies (in order to run tests from our code we will polute this clean environment with our testing dependencies, not sure yet how that can be avoided if those tests stay in current repo, obvioysly if we use dedicated repo we can avoid that)

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?