Consider explicit option flags instead of overusing force mode

[hohwille]

As a IDEasy user, I want to activate and trigger advanced features individually so that I stay in control of what is happening.
However, currently a lot of advanced features are triggered by force mode (-f or --force).
For example ide -f update triggeres the following additional features compared to ide update:

• code repo gets pulled
• all repositories are recreated and rebuild (even if they had already been setup before)
• IDE plugins are reinstalled even if they are already present (e.g. to repair broken plugin installations)

There are more features like this and I do not want to give a full spec of what -f is actually doing.
But each additional step/feature can take quite some time, can fail, can cause unwanted side-effects, etc.

Conclusion

End users would like to have more control. Therefore similar to option flags like --skip-repositories or --skip-tools or --skip-updates, we should introduce explicit options to give more control to the user.
E.g.

• ide update --pull could pull updates even in case of a code repository (see Support to allow settings in code repository #757)
• ide update --plugins could enforce that plugins are updated even if already installed
• ide update --repositories could enforce that repositories are recreated and rebuild

Open questions for discussion:

• Should the options be more explicit (--force-pull, --force-plugin-update, etc.) or do we prefer shorter names with good descriptions in the help?
• Would ide update -f then do more or less the same as ide update --pull --plugins --repositories? IMHO that would make sense.
• What would happen if I call ide update --skip-repositories --repositories? This is kind of inconsistent. However, I would prefer it to skip the repositories and maybe log a warning that --repositories will be ignored because --skip-repositories is skipping all repositories instead of making the command fail with an error.