Have a separate `e2e` infrastructure for end-to-end tests in `vdev`

[neuronull]

As part of #18533 ,

The tests there are currently using the vdev integration subcommand, and corresponding infrastructure. Yet, the tests are located in a different area of the code than the integration tests, and they are fundamentally different from integration tests.

Thus we should do a small refactor to vdev 's integration subcommand code, to be able to use the same infrastructure for a new subcommand vdev e2e.

Note that changes are in progress already to hold the docker compose and test files for the e2e tests in scripts/e2e , but this is not the complete solution just an intermediary.

### Tasks
- [x] implement `cargo vdev e2e`
- [x] implement `cargo vdev  e2e ci-paths` , and update the change.yml workflow