🐛 fix: Stop guessing URL fields from key names in config form (#38)

The admin panel's text-field renderer was inferring URL-ness from a
substring match on the field key (`url`, `endpoint`). The `endpoint`
substring matched the modelSpec preset `endpoint` field — which is a
categorical enum like `openAI`, not a URL. Rendering it as
`<input type="url">` triggered browser autofill that swallowed
uppercase keystrokes, making `openAI` and other camel-cased endpoint
values impossible to type.

Removes the keyword heuristic outright. LibreChat's configSchema today
declares zero `.url()` validations, so no field in the form should be
rendered as `type="url"`. If the schema ever tags a field with `.url()`,
detection can be added at the schema-extraction layer at that point.

Linear: AI-895

Author: dustinhealy

src/components/configuration/FieldRenderer.tsx

@@ -360,8 +360,6 @@ export function SingleFieldRenderer({
   if (controlType === 'text') {
     const stringValue = typeof currentValue === 'string' ? currentValue : '';
     const isMultiline = stringValue.includes('\n') || field.key.toLowerCase().includes('content');
-    const isUrl =
-      field.key.toLowerCase().includes('url') || field.key.toLowerCase().includes('endpoint');
 
     if (isMultiline) {
       const control = (
@@ -392,8 +390,7 @@ export function SingleFieldRenderer({
         id={fieldId}
         value={stringValue}
         onChange={(v) => onChange(path, v)}
-        placeholder={isUrl ? localize('com_ui_enter_url') : undefined}
-        type={isUrl ? 'url' : 'text'}
+        type="text"
         disabled={disabled}
       />
     );