Adopt `uv` into standard code contribution workflow

[namurphy]

It's looking rather likely that uv is the future of Python packaging, and it may be worth incorporating uv into our standard code contribution workflow.

We'll need to talk more to decide whether we want to do this, and it would probably benefit us to wait a bit longer to make this switch since the capabilities of uv are expanding quite rapidly. We'll also need to decide/prioritize which capabilities of uv we would want to adopt (i.e., uv.lock, uv add, uv remove, etc.).

In the long run, it would probably benefit us to adopt uv since it provides a more unified tool than what we're currently using. The main drawback is that it would require contributors to learn a new way of doing this. But, it would be worthwhile to do a tradeoff analysis.

Related to #2852, #2858, & #2861.