Feature/repo setup

[jfriel-oqc]

Setting up repo:

• initial code
• tests
• formatting
• repo setup, pipes etc

Note, no dependencies, pure python outside of dev dependencies

includes backwards compatibility and tests for this

[mmillmore]

Some generic comments on the structure;

1. The src folder doesn't add anything. Guides like this https://docs.python-guide.org/writing/structure/ suggest not having it
2. The test folder layout differs from our new standard testing structure at https://oxfordquantumcircuits.atlassian.net/wiki/spaces/QCAAS/pages/1614217217/Testing+Hierarchy
3. There is a script for formatting using isort, black and autoflake. We have moved away from that to use ruff, which is much faster. Also, we configure that to run on save so no script is needed

[jfriel-oqc]

Some generic comments on the structure;

1. The src folder doesn't add anything. Guides like this https://docs.python-guide.org/writing/structure/ suggest not having it
2. The test folder layout differs from our new standard testing structure at https://oxfordquantumcircuits.atlassian.net/wiki/spaces/QCAAS/pages/1614217217/Testing+Hierarchy
3. There is a script for formatting using isort, black and autoflake. We have moved away from that to use ruff, which is much faster. Also, we configure that to run on save so no script is needed

agree with removing the src, done that.

This isn't a testing structure that's agreed upon across software and seems like overkill for a stand alone library that doesn't have multiple packages or need integration testing in the same way cloud does. So not making this change here

Equally for ruff, I have no opinion here, I'm going to leave this as is currently as it's the standard for the compiler team. But if they want it to be ruff or software team in general agrees to move everything over, then I'll change this no bother. Just not going to make that decision for another team

[bgsach]

LGTM for a first pass