feat: Add autocomplete="off" to Bind DN/Password and userSearchFilter inputs in LDAPProviderDialog

[eduardomozart]

📋 Description

When configuring LDAP integration, browser-based password managers (specifically Bitwarden) incorrectly identify the Bind DN/Password and User Search Filter fields as login credentials.

Browser autocomplete on the userSearchFilter field is inappropriate — it's an LDAP filter expression (e.g. (uid={{username}})), not a user-facing value that benefits from history suggestions.

When navigating to the LDAP Configuration page, Bitwarden and other password managers should ignore these fields entirely, leaving the LDAP search strings intact and preventing accidental credential leakage into the filter configuration.

• LDAPProviderDialog.jsx: adds autoComplete="off" to the userSearchFilter Input only; all other fields are unchanged

<Input
  icon={mdiFilter}
  placeholder={T("fields.userSearchFilterPlaceholder")}
  value={form.userSearchFilter}
  setValue={set("userSearchFilter")}
  autoComplete="off"   // ← added
/>

The IconInput component already forwards autoComplete to the underlying <input> element, so no changes to shared components are needed.

🚀 Changes made to ...

• 🔧 Server
• 🖥️ Client
• 📚 Documentation
• 🔄 Other: ___

✅ Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have looked for similar pull requests in the repository and found none
• This pull request does not contain translations (translations are managed through Crowdin)

🔗 Related Issues

None.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud