Create IDEasy service

[hohwille]

This is a large and complex epic that needs to be split into smaller stories that can be implemented stepwise.
The vision and idea is that we create a background service for IDEasy that is running all the time as a process (daemon).
The end-user CLI (ide command) will then just be a simple front-end communicating with that background service.
This allows several great advantages:

• better performance: We do not need to bootstrap the IDEasy process - all is already in memory and initialized.
• this opens the door for advanced caching and we can stop writing some information to disc (e.g. cache timestamp to MTIMES of git files, maybe even git commit IDs, Module structures for Add icd command #778, etc.)
• we can implement advanced security features: during installation if admin permissions are available, we can create a dedicated user / permission for IDEasy and require that for modifying $IDE_ROOT/_ide folder that contains the software repository and additionally even all software folders in IDE_HOME projects. The end user will only have read permissions to software but cannot write or modify the installations but only IDEasy background service can do if the end-user calls according command (ide install ..., ide update, etc.).

In case you want to look at a working example using this service or daemon approach from a Java + GraalVM CLI tool, you can get inspired by mvnd that has implemented this and is already working.

So far this epic is just a vision and it needs further refinement.
Currently we have IdeContext and IdeLogger designed in a way that we start a single invocation, initialize everything for that specific case (directory, project, workspace, etc.) and after processing ramp everything down.
To create a service that is running all the time, we might need several changes in our design.
Before even trying to specify all the demands and details what to implement here, we need several rounds of refinement, brainstorming, analysis, experiments, PoCs, etc.