Draft: #45 - separate out dial_dataclass and dial_service into separate packages

[Lance-Drane]

Closes #45

This uses UV workspaces to explicitly manage dial_dataclass and dial_service as separate packages (however, both packages share a single lock file for dependencies). This is important because this allows for dial_dataclass to only have a single dependency (Pydantic) and allows us to publish that package to PyPI.

While this MR does not handle this, it may be desirable for dial_core to be its own package which depends on dial_dataclass. This could potentially cause issues with #46 though

BREAKING CHANGES

• You will have to update dial_dataclass imports to intersect_dial_dataclass. (Chosen because I think the PyPI package name should have intersect in it.)
• Installing from source with Pip changes slightly, see README for details

GIT REPO TAGS

The tags are meant to be representative of the dial_service version, which should always be updated every time we want to publish a new version. dial_dataclass versions get updated tentatively and may "skip" versions, so that its version can stay in sync with dial_service.

[Lance-Drane]

Merge conflicts have been resolved. Things to do before merging this:

• make sure that PyPI is configured to run trusted publishing
• get reviews and make sure that others can set this up

To set this up locally, you should just need to run this command:

uv sync --all-extras --all-groups --all-packages