Improve noSecrets error message

[buti1021]

If the noSecrets identifies a string as a secret based on its entropy the message should include the calculated entropy to allow efficiently tweaking the treshold (potentially aswell as the current threshold value). Additionally, point 3 of the info message should include information whether the treshold should be increased or decreased in case of a false positive which would be more useful than using the word "tweak"

  × Potential secret found.

    2527 │                                              key: "schulungsmaterial",
    2528 │                                              value: "Schulungsmaterial benötigt",
  2529 │                                              display_key: "Schulungsmaterial",
         │                                                           ^^^^^^^^^^^^^^^^^^^
    2530 │                                              display_value: "Schulungsmaterial benötigt",
    2531 │                                      },

  i Type of secret detected: Detected high entropy string

  i Storing secrets in source code is a security risk. Consider the following steps:
    1. Remove the secret from your code. If you've already committed it, consider removing the commit entirely from your git tree.
    2. If needed, use environment variables or a secure secret management system to store sensitive data.
    3. If this is a false positive, consider adding an inline disable comment, or tweak the entropy threshold. See options in our docs.
    This rule only catches basic vulnerabilities. For more robust, proper solutions, check out our recommendations at: https://biomejs.dev/linter/rules/no-secrets/#recommendations

[dyc3]

This makes sense, we should definitely output the violating entropy (if that is the trigger). See also #4113 and #4494, we are considering changing the entropy heuristic entirely.