chore: add ideInfo headers to hub reqs

[Patrick-Erichsen]

Summary by cubic

Added IDE version and prerelease status headers to all hub requests to improve request tracking and diagnostics.

• Dependencies
  • Updated internal and extension dependencies to latest patch versions.

[netlify]

❌ Deploy Preview for continuedev failed. Why did it fail? →

Name	Link
🔨 Latest commit	72001f9
🔍 Latest deploy log	https://app.netlify.com/projects/continuedev/deploys/6871e7980db5cf00097fa1ee

[cubic-dev-ai]

cubic reviewed 10 files and found no issues. Review PR in cubic.dev.

[Patrick-Erichsen]

@exigow do you know of a way to determine the release channel of an installed extension?

Our versioning schema for JB doesn't have any context on whether a given version is an EAP or stable release, they're all just 1.0.X, so not sure if we have a way to determine this.

[exigow]

@Patrick-Erichsen, AFAIK context like this is never added automatically.

I see two options:

• We could add postfix like 1.0.0-eap when building the plugin. In the projects I worked on, this was exactly how we solved it.
• We could add custom metadata to plugin.xml: we could read the channel like publishPlugin (from env vars) and add a custom tag like <channel> inside patchPluginXml. Then we could read this value from the code (I think it should be possible).

[Patrick-Erichsen]

I like option 1 of adding the -eap suffix. This would be helpful to make the release versions clearer in general imo.

I will make a Linear issue for this, but think it's okay to merge this in the meantime and just have the incorrect log info.

[github-actions]

⚠️ Conventional Commit Format

Your commit messages don't follow the conventional commit format, but this won't block your PR from being merged. We recommend downloading this extension if you are using VS Code.

Expected Format:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[RomneyDa]

@Patrick-Erichsen will wait on @exigow's input before reviewing