Option to not overwrite `resume` state?

### New feature, improvement proposal

It would be nice to have an option to not overwrite the `resume` state. It happens sometimes that b/c reasons I have to run a separate goal (or earlier module) to fix an error in the reactor build, e.g. fix formatting, or an 'earlier' module that is causing errors in the current 'later' module despite the earlier module building fine in isolation.

i can of course just use `mvn`, which is what I do at the moment, but it would be nice to have the speed/startup improvements of `mvnd` for these 'side' tasks without losing the reactor `resume` state.

The issue names no files, tests, or entry points. Start by locating mvnd’s resume-state handling and the command path for running a separate goal; clarify how an opt-out should preserve the existing state, then add coverage for the side-task scenario.

Written by the indexing model from the issue text.