test(method): improved performance in coloc tests

[xyg123]

✨ Context

Prev. implemented coloc unit tests were taking ~140 seconds, now using pytest, the coloc unit test time is ~45 secs.

🛠 What does this PR implement

Read in coloc test data using conftest.py.

🙈 Missing

None.

🚦 Before submitting

• [ x] Do these changes cover one single feature (one change at a time)?
• [ x] Did you read the contributor guideline?
• [ x] Did you make sure to update the documentation with your changes?
• [ x] Did you make sure there is no commented out code in this PR?
• [ x] Did you follow conventional commits standards in PR title and commit messages?
• [x ] Did you make sure the branch is up-to-date with the dev branch?
• [ x] Did you write any new necessary tests?
• [ x] Did you make sure the changes pass local tests (make test)?
• [ x] Did you make sure the changes pass pre-commit rules (e.g poetry run pre-commit run --all-files)?

[d0choa]

@ireneisdoomed do you mind looking at this one when you have time? Returning a list of dataframes looks a bit off.

[ireneisdoomed]

@d0choa will do!

[ireneisdoomed]

How was this file generated? For semantic tests, it's easier to understand if you create a data subset in the testing module directly.
Instead of reading a file of 500 rows, create a dataframe with 2 overlapping variants, for example.

The same testing function can be parametrised for both scenarios: associations that overlap on multiple SNPs, and on a single SNP.

[xyg123]

It was directly extracted from the test dataset from the R package

[ireneisdoomed]

@xyg123 Do we need to update the expected results or can this be merged?

[xyg123]

@xyg123 Do we need to update the expected results or can this be merged?

Yes! I think so!
Apologies, I assumed check_exact=False, check_dtype=True meant it only checking if data types were the same, I didn't realise the function was still doing a results comparison with a floating point tolerance.