cryptoki: fix QNX build and tests

[OliverHeilwagen]

• Update score crates and related Bazel dependencies for QNX-compatible Rust platform resolution, regenerating the Bazel module lockfile.
• Pin libc to the QNX-compatible 0.2.186 release.
• Select the appropriate C++ runtime linker flags for Linux and QNX builds.
• Use TEST_TMPDIR for QNX integration-test storage paths instead of /tmp.
• Add a QNX-specific mtime workaround for token-object persistence tests.
• Move optional user Bazel configuration loading after repository defaults.

[OliverHeilwagen]

@ShoroukRamzy I noticed that the former fix was skipping elements, now cryptoki lib is build and tests are running under QNX. Can you please check if my changes are valid?

[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.6.0) and connecting to it...
INFO: Invocation ID: 79cdf07b-ed31-42c0-9a8f-f56fbe3e55ed
Computing main repo mapping: 
DEBUG: Rule 'score_baselibs_rust+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-4kzcXcvGi9xBEEnrPOiSEvteITZMPKmK3MNgJXQIGtY="
DEBUG: Repository score_baselibs_rust+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:431:31: in <toplevel>
Computing main repo mapping: 
DEBUG: Rule 'score_logging+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-/Q5+YfLkbMpz5PfvOkNS7qA3ehzth4emFhTcsk4q3zQ="
DEBUG: Repository score_logging+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:431:31: in <toplevel>
DEBUG: Rule 'abseil-cpp+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-m3oGQwXp/ZTRJP+mzDWFkutCtdpYj7TgfQklSqQAhts="
DEBUG: Repository abseil-cpp+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:431:31: in <toplevel>
DEBUG: Rule 'protobuf+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-w6Cp7OiTLjHDtzbi2xixxC5wcM2biBOIsm0BqnHiTKI="
DEBUG: Repository protobuf+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:431:31: in <toplevel>
Computing main repo mapping: 
DEBUG: Rule 'grpc+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-CvN7gAlTEwtHwHW1ZoPuYL3D7aPDf8YAQZP1tWl1ggQ="
DEBUG: Repository grpc+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:431:31: in <toplevel>
Computing main repo mapping: 
Loading: 
Loading: 1 packages loaded
Loading: 1 packages loaded
    currently loading: 
Loading: 1 packages loaded
    currently loading: 
Loading: 1 packages loaded
    currently loading: 
WARNING: Target pattern parsing failed.
ERROR: Skipping '//:license-check': no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/inc_security_crypto/inc_security_crypto/BUILD
ERROR: no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/inc_security_crypto/inc_security_crypto/BUILD
INFO: Elapsed time: 11.423s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

[github-actions]

Documentation preview for this pull request is available at:
pr-196: https://eclipse-score.github.io/inc_security_crypto/pr-196/

[ShoroukRamzy]

@ShoroukRamzy I noticed that the former fix was skipping elements, now cryptoki lib is build and tests are running under QNX. Can you please check if my changes are valid?

Thank you for the PR @OliverHeilwagen, I will give my feedback soon.

[ShoroukRamzy]

Hi @OliverHeilwagen, I analyzed the test skip issue on QNX happened in this PR #191 and I agree with the current fix. The idea, score crates is configured for qnx7 triple not qnx8. That's why setting qnx8 triple in that PR led to target incompatibility, causing the tests to be silently skipped. So I agree with the current reverting to qnx7 solution as a backward-compatibility workaround at the moment. Thanks for the fix!

[ShoroukRamzy]

Hi @OliverHeilwagen, I created these PRs to allow qnx800 target compilation for score consumer repos in the future eclipse-score/rules_rust#21
and this eclipse-score/score-crates#74

[ShoroukRamzy]

Thank you for the fix @OliverHeilwagen.