Potential fix for code scanning alert no. 39: Use of password hash with insufficient computational effort

[zeroc0d3]

Potential fix for https://github.com/telemetryflow/telemetryflow-core/security/code-scanning/39

Use a slow password hashing scheme (best here: Node’s built-in crypto.scryptSync) instead of raw SHA-256 when deriving api_key_secret for storage.

Best single fix in this file:

• Keep existing functionality (store a derived secret string), but change line 322 logic to:
  • Generate a random salt per key.
  • Derive with scryptSync(secret, salt, 64).
  • Store in a self-contained format like scrypt$<saltHex>$<hashHex> so verification code can parse it later.
• This avoids adding external dependencies and satisfies CodeQL by replacing fast hash with computationally expensive KDF.

Edits are only in:

• backend/src/modules/api-keys/infrastructure/persistence/seeds/01-DefaultApiKeysSeed.ts
• Specifically around the current SHA-256 assignment for apiKeySecret.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.