feat: pull models list when setting up a new remote engine

[louis-menlo]

Describe Your Changes

Previously, when setting up a new remote provider, users had to manually set up models. With this update, as soon as users set up a new provider, it will automatically attempt to pull models from the specified /models endpoint.

Fixes Issues

• Closes roadmap: Allow Users To Add Remote Models #4515

Self Checklist

This pull request includes several changes to the JSONEngineManagementExtension class and related configuration files to enhance the handling of remote models and engines. The most important changes include modifying the Model type, updating the configuration, and improving the methods for adding and populating remote models.

Changes to Model type:

• core/src/types/model/modelEntity.ts: Renamed the mode property to model in the Model type.

Configuration updates:

• extensions/engine-management-extension/rolldown.config.mjs: Added default payload, response body, and request headers transformations to the configuration.

Enhancements to JSONEngineManagementExtension class:

• extensions/engine-management-extension/src/index.ts: Introduced a new ModelList interface for handling remote models.
• extensions/engine-management-extension/src/index.ts: Modified the getRemoteModels method to return a ModelList instead of an array of Model objects.
• extensions/engine-management-extension/src/index.ts: Enhanced the addRemoteEngine method to include default settings and optionally persist models.
• extensions/engine-management-extension/src/index.ts: Added a private populateRemoteModels method to pull and persist models from the remote provider.

[github-actions]

Barecheck - Code coverage report

Total: 67.86%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

[github-actions]

This is the build for this pull request. You can download it from the Artifacts section here: Build URL.