Integration with AppInsights

### Severity

P4 - Low (Cosmetic/minor inconvenience)

### Describe the Bug with repro steps

Accoring to the documentation
https://learn.microsoft.com/en-us/azure/logic-apps/enable-enhanced-telemetry-standard-workflows?tabs=portal#query-trigger-and-action-events-by-workflow-run-id
when you integrate logic app with AppInsights the Requests.Operation_id column contains the workflowRunId value.
In fact, the default behavior now with the host.json generated by VSCode is different. It appears the OperationId by default now is Incoming OperationId, whatever it may be in different scenarios.
To make the AppInsights integration to behave the default way that @kewear mentioned in his video https://www.youtube.com/watch?v=ZaJM_wFliMM - that is the OperationId = workflowRunId, you now have to manually add
to your host.json the part below:
"extensions":{
"workflow":{
"Settings": {
**"Runtime.ApplicationInsightTelemetryVersion": "v2"**
}
}
}

If you didn't add the part above manually, the default behavior would as if you specified these two properties:
"extensions":{
"workflow":{
"Settings": {
**"Runtime.ApplicationInsightTelemetryVersion": "v2"**
**"Runtime.ApplicationInsights.PreserveIncomingOperationId": "true"**
}
}
}

Please add the required entries to the VSCode generated host.json or/and update the documentation. It may save people many hours of googling with pretty much no useful information, until you come across the video and start experimenting with the settings.

### What type of Logic App Is this happening in?

Standard (VSCode)

### Are you experiencing a regression?

_No response_

### Which operating system are you using?

Windows

### Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

### Workflow JSON

```json

```

### Screenshots or Videos

_No response_

### Environment

Chrome
Ext 5.165.5

### Additional context

_No response_

Start by comparing the VSCode-generated host.json with the linked Azure Logic Apps telemetry documentation and the reported Application Insights behavior. Determine whether the generated configuration or the documentation should change; done means the documented and default OperationId behavior is consistent and clearly explained.

Written by the indexing model from the issue text.