Example type verification for sub-object errors with INVALID_TYPE

[scbedd]

This seemingly occurs where we define the type of a containing object, but not the individual properties within.

Specific Build Log Line

Error Detail:

{
  code: 'INVALID_TYPE',
  message: 'Expected type object but found type integer',
  schemaUrl: 'specification/sql/resource-manager/Microsoft.Sql/preview/2023-02-01-preview/DatabaseAdvisors.json',
  exampleUrl: 'specification/sql/resource-manager/Microsoft.Sql/preview/2023-02-01-preview/examples/DatabaseRecommendedActionListExpand.json',
  schemaPosition: { line: 409, column: 35 },
  schemaJsonPath: '#/properties/details/additionalProperties/type',
  examplePosition: { line: 602, column: 38 },
  exampleJsonPath: "$responses.200.body[3].properties.recommendedActions[0].properties.details['sqlErrorCount']",
  severity: 0,
  source: 'response',
  operationId: 'DatabaseAdvisors_ListByDatabase',
  level: '\x1B[31merror\x1B[39m'
}

Here is the schema detail:

        "details": {
          "description": "Gets additional details specific to this recommended action.",
          "type": "object",
          "additionalProperties": {
            "type": "object"
          },
          "readOnly": true
        }

With example:

                  "details": {
                    "sqlErrorNumber": 208,
                    "sqlErrorMessage": "Invalid object name 'dbo.Companies'.",
                    "sqlErrorCount": 342482
                  }

As one can see, we are throwing on sqlErrorCount not being a string. Even though we never defined what those properties would be.

Repro Branch