🦙 refactor: Normalize Ollama Config Names

[danny-avila]

Summary

Closes #4654

I standardized the Ollama endpoint name normalization across endpoint and model configurations, improving code consistency and maintainability.

• Moved normalizeEndpointName function from loadConfigModels.js to handleText.js for centralized access
• Added JSDoc documentation to normalizeEndpointName function to clarify its purpose and parameters
• Implemented name normalization in loadConfigEndpoints.js to match the behavior in loadConfigModels.js
• Destructured configName from endpoint object and applied normalization before use
• Reordered exports in handleText.js for better readability
• Removed duplicate imports across files

Testing

To test these changes:

1. Configure custom Ollama endpoints with varying name cases (e.g., "ollama", "Ollama", "OLLAMA")
2. Verify all variations are normalized correctly in both endpoint and model configurations
3. Ensure existing endpoint functionality remains intact
4. Check that the normalized names are consistently used throughout the application

Test Configuration:

• Custom Ollama endpoint configurations
• Various case variations of "ollama" in endpoint names