fix: HttpContextProvider handle null uri field

[Ayyanaruto]

Description

• Add a null check in HttpContetProvider uri field
• Add a test to check whether it works
• fix HTTP provider fails to work in Continue v1.0.19 and later versions #6790

Checklist

• I've read the contributing guide
• The relevant docs, if any, have been updated or created
• The relevant tests, if any, have been updated or created

Tests

HttpContextProvider.test.ts

---

Summary by cubic

Fixes HttpContextProvider to safely handle null or missing uri values without throwing. Prevents crashes when servers omit the uri field.

• Bug Fixes
  • Construct uri with item.uri && { ... } to avoid TypeErrors.
  • Added tests covering valid, missing, null, mixed-array, defaults, and partial uri cases.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Ayyanaruto]

I have read the CLA Document and I hereby sign the CLA

[Ayyanaruto]

recheck

[cubic-dev-ai]

No issues found across 2 files

[Patrick-Erichsen]

Appreciate the tests!

[Ayyanaruto]

I’m really glad that my first PR in Continue got approved thanks for reviewing it! 🎉

[sestinj]

🎉 This PR is included in version 1.28.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.25.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀