fix: fixed name field is mandatory issue

[Rutetid]

Summary

Fixes #4369

Fixes a UX mismatch where the Name field is labeled optional but required to submit.

Changes

• Aligns Knowledge settings “Add LLM Provider Key” dialog with the optional Name label.
• Allows submission without Name and falls back to provider name when blank.

Testing

All frontend test and pnpm check:ci passes

Screen Recording

2026-05-05.16-55-49.mp4

[Copilot]

Pull request overview

This PR fixes the knowledge settings “Add LLM Provider Key” dialog so the Name field truly behaves as optional, matching the UI and the linked issue. It updates the create flow in the settings page to allow blank names and substitute the selected provider’s display name.

Changes:

• Removes the Name field from the client-side submit eligibility check.
• Trims the submitted name before sending it to the create mutation.
• Falls back to PROVIDER_CONFIG[provider].name when the user leaves Name blank.

[Rutetid]

added the test pls review @copilot

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

[Rutetid]

my bad, fixed the lint error

[Konstantinov-Innokentii]

If backend requires name, maybe just let's make it required in UI?

[Rutetid]

If backend requires name, maybe just let's make it required in UI?

@Konstantinov-Innokentii , in this implementation we are falling back to the model name if the user does not provide any name, so we can do that or as you said we can make it mandatory in the UI itself.

Which implementation should we go forward with?

[Konstantinov-Innokentii]

If it's required on backend, let's just make it required on frontend too?