this basically does what the MbrCommand does, but in the UI. You can update a central.mvn index file with this action.
There is a DryRun option, which just copies the result to clipboard without touching the index file. you can use that to simulate it and check the result upfront.

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

and add options for scope MICRO, MINOR and MAJOR
Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

now it looks like MbrCommand#_check which is a string table showing the current and new version - basically a preview
e.g.
## Updates available
com.fasterxml.jackson.core:jackson-core:2.16.1                        2.16.2

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

TODO investigate into suggestion of using Result instead of outputing

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

Since MbrUpdater should not print out directly any logging statements, I tried to do it outside in MbrCommand. Because MbrCommand also did the logging before, so I tried do it in a similar way, to preserve existing behavior.

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

the new container obj allows to better track when we got a version from the mavencentral-fetch, and this in turn allows us to write the logging output the same way as it was before in MbrCommand

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>