callback operationId is not included in dispute resolving.

[davidjlynn]

I have an API which when merged with another API results in operationId conflicting. Particularly this occurs when using callbacks, but these have a unique value per API, and I would expect this to be part of the dispute functionality.

When running this through a validator afterwards it results in an error:

Errors:
        -attribute paths.'/url'(post).callbacks(post).operationId is repeated

I suspect a fix would be to handle this like other disputes (prefix/suffix)