fix: remove duplicate message calls in handleSubmit causing profile state sharing

When editing profile B while profile A is active, the handleSubmit function
had a duplicate block that was:
1. Sending updateCondensingPrompt twice (line 560 and removed duplicate)
2. Sending upsertApiConfiguration to currentApiConfigName (active profile A)
   instead of editingApiConfigName (profile B being edited)
3. Sending telemetrySetting twice (line 564 and removed duplicate)

The duplicate upsertApiConfiguration call caused both profiles to receive
identical configuration when saving, explaining the bug where 'change B,
then A gets the same changes'.

The duplicate code block appears to be leftover from before PR #3732's
profile isolation changes, likely kept during the merge in PR #3895.

Fixes the profile state sharing bug reported after PR #3895 merge.

Author: markijbema

webview-ui/src/components/settings/SettingsView.tsx

@@ -586,12 +586,6 @@ const SettingsView = forwardRef<SettingsViewRef, SettingsViewProps>(({ onDone, t
 			// Update cachedState to match the current state to prevent isChangeDetected from being set back to true
 			setCachedState((prevState) => ({ ...prevState, ...extensionState }))
 
-			// These have more complex logic so they aren't (yet) handled
-			// by the `updateSettings` message.
-			vscode.postMessage({ type: "updateCondensingPrompt", text: customCondensingPrompt || "" })
-			vscode.postMessage({ type: "upsertApiConfiguration", text: currentApiConfigName, apiConfiguration })
-			vscode.postMessage({ type: "telemetrySetting", text: telemetrySetting })
-
 			// kilocode_change: When editing a different profile, don't overwrite apiConfiguration
 			if (editingApiConfigName !== currentApiConfigName) {
 				// Only sync non-apiConfiguration fields from extensionState