[BUG] `Microsoft.DataFactory` - `IntegrationRuntimes_Get` does not return `InteractiveQueryProperties`

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/datafactory/resource-manager/Microsoft.DataFactory/DataFactory/stable/2018-06-01/datafactory.json#L755

### API Spec version

2018-06-01

### Describe the bug

The `IntegrationRuntimes_Get` operation doesn't return the `InteractiveQueryProperties` [object](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/datafactory/resource-manager/Microsoft.DataFactory/DataFactory/stable/2018-06-01/entityTypes/IntegrationRuntime.json#L104-L129).

This is preventing us from managing Interactive Query/Authoring TTL in the AzureRM Terraform provider as we're unable to retrieve the value to detect drift.

The [IntegrationRuntimes_GetStatus](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/datafactory/resource-manager/Microsoft.DataFactory/DataFactory/stable/2018-06-01/datafactory.json#L909) operation does return the interactive authoring properties however they're not included in the [ManagedIntegrationRuntimeStatusTypeProperties definition](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/datafactory/resource-manager/Microsoft.DataFactory/DataFactory/stable/2018-06-01/entityTypes/IntegrationRuntime.json#L879) so our generator doesn't include these fields in our SDK

### Expected behavior

The `IntegrationRuntimes_Get` operation returns the `InteractiveQueryProperties` object

### Actual behavior

`InteractiveQueryProperties` object is not returned

### Reproduction Steps

Create Integration Runtime with managed vnet:
```
PUT https://management.azure.com/subscriptions/{SubscriptionID}/resourceGroups/{ResourceGroupName}/providers/Microsoft.DataFactory/factories/{FactoryName}/integrationRuntimes/{IntegrationRuntimeName}?api-version=2018-06-01
{
"name": "{name}",
"properties": {
"description": "",
"managedVirtualNetwork": {
"referenceName": "default",
"type": "ManagedVirtualNetworkReference"
},
"type": "Managed",
"typeProperties": {
"computeProperties": {
"dataFlowProperties": {
"cleanup": true,
"computeType": "General",
"coreCount": 8,
"timeToLive": 0
},
"location": "autoresolve"
}
}
}
}
```

Enable Interactive Query/Authoring:

```
POST https://management.azure.com/subscriptions/{SubscriptionID}/resourceGroups/{ResourceGroupName}/providers/Microsoft.DataFactory/factories/{FactoryName}/integrationRuntimes/{IntegrationRuntimeName}/enableInteractiveQuery?api-version=2018-06-01

{
"autoTerminationMinutes": 30
}
```

Wait for the async operation to complete, then perform a GET:

```
GET https://management.azure.com/subscriptions/{SubscriptionID}/resourceGroups/{ResourceGroupName}/providers/Microsoft.DataFactory/factories/{FactoryName}/integrationRuntimes/{IntegrationRuntimeName}?api-version=2018-06-01
```

### Environment

_No response_

Compare the IntegrationRuntimes_Get response in specification/datafactory/resource-manager/Microsoft.DataFactory/DataFactory/stable/2018-06-01/datafactory.json with InteractiveQueryProperties in entityTypes/IntegrationRuntime.json. Also inspect ManagedIntegrationRuntimeStatusTypeProperties there, then update the referenced definitions so the GET response exposes the object and status properties. Done means the specification represents the expected InteractiveQueryProperties fields for both operations.

Written by the indexing model from the issue text.