refactor: Rename all remaining conduwuit references to Continuwuity

Also adds an alias for the old binary name to the dockerfile

Supersedes !1485
Closes #1536
Closes #2277

docs/development/code_style.mdx

@@ -184,7 +184,7 @@ debug!(
 Use the `WithLock` trait from `core::utils::with_lock`:
 
 ```rs
-use conduwuit::utils::with_lock::WithLock;
+use continuwuity::utils::with_lock::WithLock;
 
 // Good - explicit closure guard
 shared_data.with_lock(|data| {
@@ -205,7 +205,7 @@ shared_data.with_lock(|data| {
 For async contexts, use the async variant:
 
 ```rs
-use conduwuit::utils::with_lock::WithLockAsync;
+use continuwuity::utils::with_lock::WithLockAsync;
 
 // Good - async closure guard
 async_shared_data.with_lock(|data| {

docs/development/index.mdx

@@ -56,7 +56,7 @@ workspace crate(s) must define the feature there in its `Cargo.toml`.
 
 So, if this is adding a feature to the API such as `woof`, you define the
 feature in the `api` crate's `Cargo.toml` as `woof = []`. The feature definition
-in `main`'s `Cargo.toml` will be `woof = ["conduwuit-api/woof"]`.
+in `main`'s `Cargo.toml` will be `woof = ["continuwuity-api/woof"]`.
 
 The rationale for this is due to Rust / Cargo not supporting ["workspace level
 features"][9], we must make a choice of; either scattering features all over the

docs/development/testing.mdx

@@ -12,7 +12,7 @@ Install Git, Rust, Docker, Go, and `jq`. From this repository's root, build the
 server image and run the suite:
 
 ```bash
-cargo build -p conduwuit
+cargo build -p continuwuity
 docker build -t continuwuity:complement -f docker/complement.Dockerfile .
 ./bin/complement
 ```