Carry over requestOptions from config to completion modles

[splatch]

Description

The configuration handling of models and completion models is fairly similar, however they differ in carrying over request options. This PR attempts to align both parts to have common logic which accepts config level request options to be taken into account.

Checklist

• The relevant docs, if any, have been updated or created
• The relevant tests, if any, have been updated or created

Screenshots

No UI changes.

Testing instructions

With this PR request options set at the config level should be considered also at tabCompletionModel level.

[netlify]

✅ Deploy Preview for continuedev ready!

Name	Link
🔨 Latest commit	d0b8c45
🔍 Latest deploy log	https://app.netlify.com/sites/continuedev/deploys/67e2eecb2b0e190008edd70a
😎 Deploy Preview	https://deploy-preview-4813--continuedev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sestinj]

@splatch before looking deeper into this PR, it would be helpful to understand how you're using requestOptions—right now we don't support top-level requestOptions in config.yaml (https://docs.continue.dev/reference) and we don't currently have plans to. If that continues to be the case, I don't think we would want to merge this, given we are eventually going to move toward YAML format

[splatch]

Hello @sestinj, reason for above changes was inability to get requestOptions for completion models. If you will have a look again on the change set there is one extra line: applyRequestOptionsToModels(tabAutocompleteModels, config);.
Without it you can't pass any options to completion models. So even if that part of configuration relies on same ModelDescription as models, it doesn't work.

I was stuck with 1.0.2 release of jetbrains plugin which worked with config.json, thus I started my patchwork from that place.

[sestinj]

sure, this makes sense and the PR is good to go once these tests re-run.

what I'm wondering is more of just which of the request options you find helpful (a bit of user research into how people are using them : ))

[splatch]

Hah, nothing special. Got a ollama instance behind nginx with self signed ssl certificate in front. Intellij have had hard times reaching it without requestOptions set.