chore: improve ci pipeline by adding lint and test jobs

[TommoLeedsy]

This PR adds lint and test jobs to the CI pipeline

[Will-Mann-16]

Is this needed as the purpose of the CI was to publish the next version (tag it) so what happens if it fails?

[TommoLeedsy]

I think this is very useful to test the code one its in main, its standard practice, also at the moment the CI is setup so that the release job will run independently of the lint and test jobs but there is something to be said for this not to be the case as it would mean that we don't tag releases with falling tests? Moving to that setup where release depends on the other jobs in the pipeline passing would also mirror how we have it setup in astra.