Recognizable Volume Names

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

For local development, currently volumes created by Aspire have a cryptic name, like `1ad80f9e6e2e77f45a9048408a42d05443f19afde9068cff853c197f96263924`.
It makes it difficult to associate Aspire-managed volumes with their corresponding projects and services/containers.

My current use case was to find and delete the data volume of my PostgreSQL to reset my database to scratch. It was not trivial.

Compare this to e.g. compose, where the volumes are neatly named:

```
➜ podman volume ls
DRIVER VOLUME NAME

# compose
local keycloak-configuration_postgres_data
local keycloak-configuration_extension
local keycloak-configuration_themes
local keycloak-configuration_keycloak-data

# aspire
local ticketshop.aspire.apphost-f247ba5932-storage-data
local c14567a276c416bcfde5416f02236ad335c61855fc90f2a28d1b247adcac3448
local 2d98a89734ea8da42197762aa4fe8cbfa3618f5bc8687fb6192b1199ac88de9e
local 47b587610267bcf347d3d85d3224f0f11ecef4c94bbe6dabfea3d92eb9d296cf
local c643be77f7244a407b4cbbd8f1ed138f61aec4c9a65a88fdef4184fedd7d8d08
local de37fcd4092519b1b6f5a2efd9322093bdd026d95e45ea83b1cf39396f636301
local 8def9f74cc5295ca9185f8a019f6903f274954f544e33bc79b556dc8cdfec10b
```

### Describe the solution you'd like

Follow a naming schema for the volumes. I suggest something along the lines of `aspire-[project-name]-[service-name]-[voluma-name-or-usage]`, e.g. `aspire-ticketshop-postgres-data` or `aspire-ticketshop-azurite-data`.

### Additional context

To me, it'd be a bonus if there was a trivial way to remove all Aspire-managed volumes for a given project, like `podman compose down -v` does. Like a `Hard-reset this project` action in the Aspire dashboard.

The issue does not name files or tests. Start by tracing how Aspire creates local-development volumes and what project, service, and usage context is available; done means generated volumes have recognizable stable names and the project-level cleanup behavior requested in the issue is addressed.

Written by the indexing model from the issue text.