Fix intent telemetry (#6779) (#6795)

This fixes a regression in the intent telemetry (described
[here](https://linear.app/sourcegraph/issue/SPLF-330), originally fixed
in #6637). Two fixes:
- we weren't using the right fields in `commonProps`, meaning that the
values weren't assigned to the message and thus weren't accessible in
the chat controller where we emit metadata.
- we were accidentally overriding the `userSpecifiedIntent` field with
`auto` because of operator precedence.

We now get the correct data emitted in the `chat/executed` telemetry
events.

I want to backport this to vscode-1.64 and jb-7.12. Why? Telemetry data
will help us improve intent detection significantly and it's important
we have the pipeline functioning well at launch. Furthermore, the
changes are quite low-risk.



## Test plan
Tested manually.

(cherry picked from commit 1049a20)

vscode/src/chat/chat-view/ChatController.ts

@@ -832,7 +832,7 @@ export class ChatController implements vscode.Disposable, vscode.WebviewViewProv
 
         recorder.setIntentInfo({
             userSpecifiedIntent:
-                manuallySelectedIntent ?? this.featureCodyExperimentalOneBox ? 'auto' : 'chat',
+                manuallySelectedIntent ?? (this.featureCodyExperimentalOneBox ? 'auto' : 'chat'),
             detectedIntent: detectedIntent,
             detectedIntentScores: detectedIntentScores,
         })

vscode/webviews/chat/Transcript.tsx

@@ -350,8 +350,8 @@ const TranscriptInteraction: FC<TranscriptInteractionProps> = memo(props => {
 
             const commonProps = {
                 editorValue,
-                intent,
-                intentScores,
+                preDetectedIntent: intent,
+                preDetectedIntentScores: intentScores,
                 manuallySelectedIntent:
                     intentFromSubmit ||
                     manuallySelectedIntent.intent ||