feat: move atuin-server to its own binary (#3112)

A combined binary was an early dev decision, when I thought most users
would be self hosting. It is now clear that in actual fact, most users
do not self host. So let's avoid forcing every user to have a copy of
the server literally linked in, and let's stop building server deps over
and over.

The deployment for this shouldn't change. `dist` will build a binary for
this automatically, and will also add it to the installer. The latter is
perhaps something we should explore changing too!

<!-- Thank you for making a PR! Bug fixes are always welcome, but if
you're adding a new feature or changing an existing one, we'd really
appreciate if you open an issue, post on the forum, or drop in on
Discord -->

## Checks
- [ ] I am happy for maintainers to push small adjustments to this PR,
to speed up the review cycle
- [ ] I have checked that there are no existing pull requests for the
same thing

1 files changed, 1 insertions, 1 deletions

diff --git a/.github/workflows/rust.yml b/.github/workflows/rust.yml
index 85d5e5d9..7f9b644b 100644
--- a/.github/workflows/rust.yml
+++ b/.github/workflows/rust.yml
@@ -147,7 +147,7 @@ jobs:
         run: cargo check --no-default-features --features sync --workspace
 
       - name: Run cargo check (server)
-        run: cargo check --no-default-features --features server --workspace
+        run: cargo check -p atuin-server
 
       - name: Run cargo check (client only)
         run: cargo check --no-default-features --features client --workspace