Repository: Avaiga/taipy
Pull request: align core service logs
Resolves #803

Problem statement:
Align Core service logs.
**Description**
Here is an example of the logs generated by running a core service, executing two tasks and stopping the service. 
```
[2024-02-07 10:27:44][Taipy][INFO] Start job dispatcher...
[2024-02-07 10:27:48][Taipy][INFO] job JOB_arima_training_7d61b95e-4998-4696-953b-ff74179f06b3 is completed.
[2024-02-07 10:27:49][Taipy][INFO] job JOB_arima_scoring_9c374054-cd38-4abf-82bd-28f43c33de56 is completed.
[2024-02-07 10:27:49][Taipy][INFO] Core service has been stopped.
```
Running the core service actually adds a log about starting a job dispatcher. 
1. This is inconsistent regarding the log generated when stopping the service, 
2. Running the core service does more than just starting a job dispatcher

Any change on that should be reflected in the documentation (user manual, reference manual, demos, tips and tricks, etc...)

**Solution proposed**
Remove the log "Start job dispatcher..." and add a new log "Core service started..."

**Acceptance Criteria**
- [ ] The log should be consistent and representative of what is done.
- [ ] Ensure new code is unit tested, and check code coverage is at least 90%
- [ ] Ensure the documentation sets are updated

Hints from issue discussion:

Commit message: add Core service started... to Core.run()

Patch to review:
diff --git a/taipy/core/_core.py b/taipy/core/_core.py
index 413927fd63..f85122321a 100644
--- a/taipy/core/_core.py
+++ b/taipy/core/_core.py
@@ -61,6 +61,7 @@ def run(self, force_restart=False):
             self.__class__._is_running = True
 
         self._manage_version_and_block_config()
+        self.__logger.info("Core service started...")
         self.__start_dispatcher(force_restart)
 
     def stop(self, wait: bool = True, timeout: Optional[float] = None):
diff --git a/taipy/core/_orchestrator/_dispatcher/_job_dispatcher.py b/taipy/core/_orchestrator/_dispatcher/_job_dispatcher.py
index 16d66b61c1..af28018fc8 100644
--- a/taipy/core/_orchestrator/_dispatcher/_job_dispatcher.py
+++ b/taipy/core/_orchestrator/_dispatcher/_job_dispatcher.py
@@ -61,7 +61,7 @@ def stop(self, wait: bool = True, timeout: Optional[float] = None):
             self.join(timeout=timeout)
 
     def run(self):
-        self._logger.info("Start job dispatcher...")
+        self._logger.debug("Start job dispatcher...")
         while not self._STOP_FLAG:
             try:
                 if self._can_execute():
@@ -77,7 +77,7 @@ def run(self):
             except Exception as e:
                 self._logger.exception(e)
                 pass
-        self._logger.info("Job dispatcher stopped.")
+        self._logger.debug("Job dispatcher stopped.")
 
     def _can_execute(self) -> bool:
         """Returns True if the dispatcher have resources to execute a new job."""


Code review comments:
diff_hunk: @@ -61,7 +61,7 @@ def stop(self, wait: bool = True, timeout: Optional[float] = None):
             self.join(timeout=timeout)
 
     def run(self):
-        self._logger.info("Start job dispatcher...")
+        self._logger.debug("Start job dispatcher...")
path: taipy/core/_orchestrator/_dispatcher/_job_dispatcher.py
text: @user1:
What do you think?
```suggestion
        self._logger.debug("Job dispatcher started...")
```

@author:
I think may be `Job dispatcher starting...`  is better?

@author:
Yeah, i think `Job dispatcher started...` is better. thanks! What confuse me is the `...`  and ` started` seems not suitable