fix: exclude undefined max token fields from settings export

[roomote]

Description

This PR fixes an issue where exported settings incorrectly included modelMaxTokens and modelMaxThinkingTokens fields for models that don't support reasoning budgets.

Problem

• When exporting settings, the JSON included max token fields even for models that don't support reasoning budgets
• These fields were showing as undefined in the exported JSON, creating misleading/invalid configuration
• The UI correctly only shows token sliders for models with reasoning budget support, but the export didn't respect this

Solution

• Modified the ProviderSettingsManager.export() method to exclude modelMaxTokens and modelMaxThinkingTokens fields when they are undefined
• This ensures only models that have explicitly set values for these fields will include them in the export
• Added comprehensive test coverage to verify the fix works correctly

Testing

• Added new test case that verifies undefined fields are properly excluded from export
• Test covers multiple scenarios: completely undefined fields, partially defined fields, and fully defined fields
• All existing tests continue to pass
• Type checking and linting pass

Fixes #7944

---

Important

Fixes export issue in ProviderSettingsManager by excluding undefined max token fields, with comprehensive test coverage added.

• Behavior:
  • ProviderSettingsManager.export() now excludes modelMaxTokens and modelMaxThinkingTokens if undefined, ensuring only explicitly set values are exported.
• Testing:
  • Added test in importExport.spec.ts to verify exclusion of undefined fields during export.
  • Test scenarios include: completely undefined fields, partially defined fields, and fully defined fields.
  • All existing tests pass, ensuring no regressions.
• Misc:
  • Fixes issue [BUG] Export includes max token fields for unsupported models #7944.

^{This description was created by for 5a01505. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Reviewing my own code because apparently I trust no one, not even myself.

[roomote]

The use of as any here works, but have you considered a more type-safe approach? We could check if these properties exist in the discriminated union type or use a type guard. Something like:

Suggested change

	const configAny = config as any
	// Remove max token fields if they are undefined
	// These fields should only be included for models that support reasoning budgets
	// and when the user has explicitly set values
	if ('modelMaxTokens' in config && config.modelMaxTokens === undefined) {
	delete config.modelMaxTokens
	}
	if ('modelMaxThinkingTokens' in config && config.modelMaxThinkingTokens === undefined) {
	delete config.modelMaxThinkingTokens
	}

[roomote]

Could we extract this logic into a helper function to avoid duplication and improve maintainability? For example:

function removeUndefinedTokenFields(config: any): void {
  if (config.modelMaxTokens === undefined) {
    delete config.modelMaxTokens
  }
  if (config.modelMaxThinkingTokens === undefined) {
    delete config.modelMaxThinkingTokens
  }
}

Then just call removeUndefinedTokenFields(config) here. This would make it easier to add more fields in the future if needed.

[roomote]

Excellent test coverage! The test thoroughly covers all scenarios: completely undefined fields, partially defined fields, and fully defined fields. This gives confidence that the fix works correctly.

[daniel-lxs]

Maybe we should check for supportsThinkingBudget instead of checking for undefined because these values might exist on profiles if the model was switched from one that has supportsThinkingBudget and one that doesn't.

Closing for now.