Feature request: Need strategy for resolution calculations when using split-merge

How did you install OpenDroneMap? (Docker, natively, ...)?
Natively

What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/)
irrelevant

What is the problem?

When we run with split-merge, we can specify the preferred resolution. For some submodels we might get that preferred resolution, for others, we might receive messages like the following:

[WARNING] Maximum resolution set to GSD - -300% (28.07 cm / pixel, requested resolution was 15.0 cm / pixel)
[WARNING] Maximum resolution set to GSD - 10.0% (6.32 cm / pixel, requested resolution was 5.0 cm / pixel)

What should be the expected behavior? If this is a feature request, please describe in detail the changes you think should be made to the code, citing files and lines where changes should be made, if possible.

I'm really not sure. But we should consider keeping a consistent resolution across all the submodels.

How can we reproduce this? (What steps did you do to trigger the problem? What parameters are you using for processing? If possible please include a copy of your dataset uploaded on Google Drive or Dropbox. Be detailed)

The issue provides no files, tests, or parameters to follow. Start by tracing how split-merge calculates and reports resolution for submodels, then define the expected behavior for keeping resolution consistent and determine how the warning cases should be handled.