feat(scope): Improve logging about backends

Hello!

Use case

I recently hit a case where s3 backend has problem, and it trigger error inside OCTI.

However, the error said:

{"category":"APP","cause":{"code":"UNKNOWN_ERROR","message":"Timeout checking storage health","name":"Error","stack":"Error: Timeout checking storage health\n    at Timeout._onTimeout (file:///opt/opencti/build/back.mjs:291725:98)\n    at listOnTimeout (node:internal/timers:585:17)\n    at process.processTimers (node:internal/timers:521:7)"},"level":"error","message":"Error in health check","source":"backend","timestamp":"2026-09-16T01:00:57.034Z","version":"7.260910.0"}

And I was not sure if storage was about s3 or elasticsearch.

Current workaround

I then understand that s3 is seen as storage, and elastic as database, so able to locate and solve the problem

However, I think it could be interesting to improve logging to add the real backend name, as it's done when octi starts and tell "s3 ok", "elastic ok", and so on :-)

Proposed solution

Something like

"message":"Timeout checking S3 storage health"

Should be perfect! And same for potential elastic, redis or rabbit errors

Thank you a lot!

Yes / No (help can be provided if you need assistance submitting a PR)