Trial-adopt migration to `uv` from copier template

[callumforrester]

Blueapi has been chosen as a guinea pig project for the migration to uv in DiamondLightSource/python-copier-template#248.

Initially we believed that we could do the migration, alias pip to uv pip and keep a consistent developer experience, however various subtle differences mean we will probably have to migrate over fully and start using commands like uv sync instead of pip install. Had we known this from the start we probably would have tried the changes in a guinea pig project first, so we will now do that. The plan is:

• Finish getting blueapi onto the latest release of the copier template chore: Update python-copier-template to 3.0.0 #944 chore: Update to copier template v4 #1077
• Adopt the branch in refactor: Convert to use uv python-copier-template#248 into blueapi
• Fix any issues that prevent development, build, release, deployment etc.

After that, we will evaluate it for a while, see how easy it is to live with, make QOL improvements etc. and when we are happy, push those back into the copier template.

Acceptance Criteria

• The tickboxes above are done
• Blueapi still builds, runs and deploys
• pip install is not a required part of any blueapi workflow