feat: move cortex extension settings to local engine page

[louis-jan]

Describe Your Changes

This PR is to update app local engine settings which extended from it's parent extension settings. From now on, there is no Cortex extensions page, but all settings moved to llama.cpp engine page.

Fixes Issues

• Closes enhancement: Move settings in Cortex page to llama.cpp page #4441

Changes

This pull request includes several changes to the Settings screen in the web application, primarily focusing on the ExtensionSetting component and related files. The changes introduce new functionality, improve existing code, and fix minor issues.

Changes to ExtensionSetting component:

• Updated ExtensionSetting to accept an optional extensionName prop and use useMemo to determine the current extension name. This allows for more flexible usage of the component. [1] [2] [3]
• Added import of ExtensionSetting in LocalEngineSettings.tsx and included it in the component's JSX structure. This integrates the ExtensionSetting component into the LocalEngineSettings screen. [1] [2]

Other improvements and fixes:

• Adjusted the width of the text input for number types in SettingDetailTextInputItem to improve the layout.
• Simplified the conditional class assignment in SettingDetailItem to remove unnecessary mx-4 class.
• Wrapped ExtensionSetting in a div with mx-4 class in SettingDetail to ensure consistent padding.
• Filtered out extensions with names containing 'Cortex' in SettingLeftPanel to exclude them from the settings list.

[github-actions]

Barecheck - Code coverage report

Total: 69.26%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered