Publish to crates.io

[giggio]

It would help a lot.
Other repos are taking a dependency on this project, using git. Publishing to crates.io would help.
Related to #98.

[TimeToBuildBob]

This is a reasonable request. The crates most useful to downstream projects would be aw-client-rust (for making API calls) and aw-models (for the data types).

The main challenges with publishing to crates.io:

• The workspace has tight interdependencies between crates, so they'd need coordinated versioning
• The API isn't fully stabilized yet, so semver management across multiple crates adds maintenance burden
• Some crates have build-time dependencies (like bundling aw-webui assets) that complicate clean publishing

aw-client-rust would be the highest-value crate to publish first since that's what external projects typically need. It has a relatively clean API surface.

For now, using a git dependency is the supported approach. If there's demand from multiple downstream projects, we can look at publishing aw-client-rust + aw-models as a first step.