Removing score_logging dependency & update dependency versions for 0.7 release

[MaciejKaszynski]

Removing the score_logging dependency as we do not rely on remote logging.
This resolves:
#181

• This allowed to update other dependency versions

Note there is an issue with flatbuffers, check github.com//issues/186

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.4.2) and connecting to it...
INFO: Invocation ID: e54d0b7b-a6a2-4518-ab09-cd9fecb7b86a
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (29 packages loaded, 10 targets configured)

Analyzing: target //:license-check (83 packages loaded, 10 targets configured)

Analyzing: target //:license-check (129 packages loaded, 747 targets configured)

Analyzing: target //:license-check (144 packages loaded, 5360 targets configured)

Analyzing: target //:license-check (154 packages loaded, 5429 targets configured)

Analyzing: target //:license-check (154 packages loaded, 5429 targets configured)

Analyzing: target //:license-check (158 packages loaded, 8212 targets configured)

Analyzing: target //:license-check (161 packages loaded, 10106 targets configured)

INFO: Analyzed target //:license-check (162 packages loaded, 10232 targets configured).
[8 / 15] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache, processwrapper-sandbox ... ( 1 action running)
[13 / 16] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 1s disk-cache, processwrapper-sandbox
[14 / 16] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 24.412s, Critical Path: 2.92s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 16 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

[github-actions]

The created documentation from the pull request is available at: docu-html

[pawelrutkaq]

why this would make sense ? All exec shall use logging backend from score logging.

[MaciejKaszynski]

why this would make sense ? All exec shall use logging backend from score logging.

The logging interface is coming from baselibs, that is what we are already using. I also got the info from Ragha that the score_logging/mw/log target will be soon deprecated and it is expected for users to use score_baselibs.

[pawelrutkaq]

why this would make sense ? All exec shall use logging backend from score logging.

The logging interface is coming from baselibs, that is what we are already using. I also got the info from Ragha that the score_logging/mw/log target will be soon deprecated and it is expected for users to use score_baselibs.

Thats true, bue app needs to link backend, so we wer ejsut maybe linking wrong target from score_logging but we need to link it