fix: change docs to recommend mlflow-data volume mount as rw (#379)

#### Description of changes
Updated documented volume mount options for mlflow-data to explicitly
request read-write access. Likely needed due to recent changes around
user handling in Tesseract.

#### Testing done
Local

Co-authored-by: Alessandro Angioi <[email protected]>

Author: linusseelinger

docs/content/using-tesseracts/advanced.md

@@ -49,13 +49,13 @@ Launch the `metrics` example Tesseract with the the following volume mount and `
 MacOS and Windows with Docker Desktop requires the `host.docker.internal` hostname to access services running on the host machine:
 
 ```bash
-tesseract serve --env=TESSERACT_MLFLOW_TRACKING_URI=http://host.docker.internal:5000 --volume mlflow-data:/mlflow-data metrics
+tesseract serve --env=TESSERACT_MLFLOW_TRACKING_URI=http://host.docker.internal:5000 --volume mlflow-data:/mlflow-data:rw metrics
 ```
 
 For Linux, set your Tesseracts to use the host network and access the MLflow server at `localhost`:
 
 ```bash
-tesseract serve --env=TESSERACT_MLFLOW_TRACKING_URI=http://localhost:5000 --network=host --volume mlflow-data:/mlflow-data metrics
+tesseract serve --env=TESSERACT_MLFLOW_TRACKING_URI=http://localhost:5000 --network=host --volume mlflow-data:/mlflow-data:rw metrics
 ```
 
 The same options apply when executing Tesseracts through `tesseract run`.