Optionally, provide a comma-separated list of file suffixes that determine which Bitwarden Secure Notes should be treated as Secret file credentials.

This is useful for items that represent configuration files. Any Secure Note whose name ends with one of these suffixes (e.g., .env, .properties, .yaml) will be exposed to pipelines as a FileCredentials type.

All other Secure Notes will be treated as standard StringCredentials (secret text).