Guarantee correctness by default

### New feature, improvement proposal

Enabling this extension with the default configuration should result in a working build by default. If the user wishes to optimize things further by saying (for example) "ignore changes to plugin X's property Y" then at least then it won't come to them as a surprise when this happens.

What I'm seeing instead is that by default enabling this extension breaks builds and then we have to spend days trying to figure out what configuration options we have to add to make the build work again without fully disabling the extension. Example: https://github.com/apache/maven-build-cache-extension/issues/373

The question is: why doesn't the extension already work this way? It feels as if it's meant to do so, but it doesn't seem to work in practice. Why is that?

Start by reading the failure described in issue 373 and reproducing it with the extension's default configuration. Trace which default behavior causes the build to break and document the configuration or design decisions involved. Done means enabling the extension with defaults produces a working build, while further optimizations remain explicit.

Written by the indexing model from the issue text.