[Breaking Change] False Positive: reporting spurious/unsubstantiated 'required' status changed

The Breaking changes report for [PR 21914](https://github.com/Azure/azure-rest-api-specs/pull/21914) is reporting many 'required' status changed issues that either don't exist or are not clearly substantiated in the report. Take the first one as an example:


The ["old" link](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/datamigration/resource-manager/Microsoft.DataMigration/stable/2021-06-30/datamigration.json#L111:9) goes to:


and the ["new" link](https://github.com/Azure/azure-rest-api-specs/blob/f3378cd0785625698cd43a9e7c1da4c498f0b08f/specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-11-30-preview/datamigration.json#L111:9) goes to


The "service" parameter in the "old" version is


and in the new version


which look identical to me.

The ["old" DataMigrationService schema](https://github.com/Azure/azure-rest-api-specs/blob/dev-datamigration-2022-11-30-preview/specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/definitions/Services.json#L83)


and the [new one](https://github.com/Azure/azure-rest-api-specs/blob/dev-datamigration-2022-11-30-preview/specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-11-30-preview/definitions/Services.json#L83)


And the next level down too. I cannot find where this issue is, so I think something is broken in the tool. At the very least, if there is some property deep down that has changed its required status, please point directly to it.