[BUG] Microsoft.MachineLearningServices/workspaces/outboundRules@2024-04-01-preview returns field not defined in the swagger

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2024-04-01/machineLearningServices.json#L6216C95-L6216C103

### API Spec version

2024-04-01-preview

### Describe the bug

In the GET response of this resource, it returns fields which are not defined in the swagger. For example: "location" and "tags". And the `id` is in a incorrect format.

```json
{
"id": "acctesthenglu562/outboundRules/test21",
"location": null,
"name": "test21",
"properties": {
"category": "UserDefined",
"destination": "conda.anaconda1.org",
"status": "Active",
"type": "FQDN"
},
"systemData": null,
"tags": null,
"type": "Microsoft.MachineLearningServices/workspaces/outboundRules"
}
```

### Expected behavior

The `location` and `tags` should not be returned in the GET response because they're not supported.

And the `id` should be like `/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearningServices/workspaces/{workspaceName}/outboundRules/{ruleName}`

### Actual behavior

it returns fields which are not defined in the swagger. For example: "location" and "tags". And the `id` is in a incorrect format.

### Reproduction Steps

1. Create the outbound rule resource.
2. Call GET Api and check the response.

### Environment

_No response_

Inspect specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2024-04-01/machineLearningServices.json around line 6216 and compare the outboundRules GET schema with the reported response. Confirm whether the specification or the service behavior is responsible; done means the response and documented schema agree on location, tags, and the fully qualified resource id.

Written by the indexing model from the issue text.