docs: rename remaining pixi project to pixi workspace

docs/switching_from/conda.md

@@ -76,7 +76,7 @@ This will create a new workspace with the dependencies from the `environment.yml
 ??? tip "Exporting your environment"
     If you are working with Conda users or systems, you can [export your environment to a `environment.yml`](../reference/cli/pixi/workspace/export.md) file to share them.
     ```shell
-    pixi project export conda-environment
+    pixi workspace export conda-environment
     ```
     Additionally you can export a [conda explicit specification](../reference/cli/pixi/workspace/export.md).
 

docs/tutorials/multi_environment.md

@@ -66,7 +66,7 @@ We will add the `test` environment to our workspace to add some testing tools.
 We can do this through the command line, or by editing the `pixi.toml` file.
 Here we will use the command line:
 ```shell
-pixi project environment add test --feature test
+pixi workspace environment add test --feature test
 ```
 This will add the following to our `pixi.toml` file:
 ```toml
@@ -129,8 +129,8 @@ pixi add --feature py312 python=3.12
 
 We'll add the `test` and Python features to the corresponding environments.
 ```shell
-pixi project environment add test-py311 --feature py311 --feature test
-pixi project environment add test-py312 --feature py312 --feature test
+pixi workspace environment add test-py311 --feature py311 --feature test
+pixi workspace environment add test-py312 --feature py312 --feature test
 ```
 
 This should result in adding the following to the `pixi.toml`:
@@ -190,10 +190,10 @@ This will result in the `production` environment having the exact same versions
 This way we can be sure that the project will run in the same way in all environments.
 
 ```shell
-pixi project environment add production --solve-group prod
-pixi project environment add test --feature test --solve-group prod
+pixi workspace environment add production --solve-group prod
+pixi workspace environment add test --feature test --solve-group prod
 # --force is used to overwrite the default environment
-pixi project environment add default --feature dev --feature test --solve-group prod --force
+pixi workspace environment add default --feature dev --feature test --solve-group prod --force
 ```
 
 If we run `pixi list -x` for the environments we can see that the different environments have the exact same dependency versions.
@@ -230,7 +230,7 @@ pixi add --feature docs mkdocs
 
 Now we can add the `docs` environment without the `default` feature.
 ```shell
-pixi project environment add docs --feature docs --no-default-feature
+pixi workspace environment add docs --feature docs --no-default-feature
 ```
 
 If we run `pixi list -x -e docs` we can see that it only has the `mkdocs` dependency.