release mvnd version matching mvn embedded version

### New feature, improvement proposal

IMHO, the fact that:
1. people need to learn that `mvnd` 1.x embeds Maven 3.x and `mvnd` 2.x embeds Maven 4.0
2. people need to learn that `mvnd 1.0.4` embeds precisely `mvn 3.9.14`
is part of why Maven Daemon does not really grow in the community as much as it should

**It adds confusion**

Would it be hard in the future to release `mvnd 3.9.15` embedding `mvn 3.9.15`, `mvnd 3.10.0` embedding `mvn 3.10.0`, `mvnd 4.0.0-rc-6` embedding `mvn 4.0.0-rc-6`?

notice: IIUC, one dream future feature is to decouple `mvnd` from `mvn`, aka. letting one `mvnd` launch many different `mvn` versions (by downloading them instead of embedding them): pointer welcome if it exists

I imagine that at that time, we can have a new version 5, or 6 if Maven 5 is already out

No files, tests, or entry points are named. Start by reviewing the release process and how the embedded Maven version is selected; done would require an agreed versioning design and matching mvnd releases for the embedded Maven versions, including how decoupled Maven versions should work.

Written by the indexing model from the issue text.