fix: mount vroom volume to the storage option default

[bmckerry]

The filestore.profile-options storage location defaults to /tmp/sentry-profiles. This changes the volume mount source to be the same as the option default.

[sentry]

Bug: Docker bind mount to /tmp/sentry-profiles fails because the host directory is not created, preventing vroom service startup.
_{Severity: CRITICAL | Confidence: 1.00}

🔍 Detailed Analysis

The configuration in devservices/config.yml changes the vroom service to use a host path bind mount to /tmp/sentry-profiles instead of a Docker named volume. When a developer attempts to run the vroom service via devservices, Docker will fail to start the container because the host directory /tmp/sentry-profiles does not exist. There is no logic in the Dockerfile, vroom code, or setup scripts to create this directory, nor is there documentation requiring developers to pre-create it.

💡 Suggested Fix

Ensure the /tmp/sentry-profiles host directory is created before the Docker container attempts to bind mount it. This can be achieved by adding a mkdir command to a setup script or the Dockerfile, or by reverting to a Docker named volume.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: devservices/config.yml#L26

Potential issue: The configuration in `devservices/config.yml` changes the vroom service
to use a host path bind mount to `/tmp/sentry-profiles` instead of a Docker named
volume. When a developer attempts to run the vroom service via devservices, Docker will
fail to start the container because the host directory `/tmp/sentry-profiles` does not
exist. There is no logic in the Dockerfile, vroom code, or setup scripts to create this
directory, nor is there documentation requiring developers to pre-create it.

_{Did we get this right? 👍 / 👎 to inform future reviews.}