Run as 'Tool' rather than a Dependency

[KyleKing]

Describe the solution you'd like

Instead of adding calcipy as a dependency, refactor to run calcipy as a tool with uvx, pipx, etc.

Is your feature request related to a problem? Please describe.

1. There can be dependency conflicts that complicate or prevent install
2. Taking the approach of running calcipy as a tool will lead to more generic tasks
3. calcipy can drop support for older versions of Python at EOL (https://endoflife.date/python) because the Python tool is installed separately of the code
4. Switching to a tool design approach might help with adoption because there is
5. calcipy can already be run as a tool for some, but not all tasks. Switching to a tool completely would remove ambiguity
6. Could remove the complexity of managing extras when there is one global tool install and install size doesn't need to be optimized for

Caveats

1. Not all tasks can be run from a tool and must be installed in the same environment
   • If dependencies need to be installed in the target environment, the best option would likely be nox
2. Switching to a tool could impact per-directory version management if people aren't using asdf, mise, or similar, but installing calcipy into the .venv shouldn't make a difference