Bug: no details when securitySchemes.*.name changes

Description

When a change is introduced solely to the name property of an apiKey securitySchemes object in an OpenAPI 3.1 specification, openapi‑diff merely reports that a change occurred without providing any line‑level detail (path, field changed, old and new values).In addition, there appears to be no way to disable this rule via the usual options. (incompatible.security.scheme.scheme.change:false)

old.json
new.json

==========================================================================
==                            API CHANGE LOG                            ==
==========================================================================
                             **** Restful API
--------------------------------------------------------------------------
--                            What's Changed                            --
--------------------------------------------------------------------------
- GET    /rest/v1/info
--------------------------------------------------------------------------
--                                Result                                --
--------------------------------------------------------------------------
                   API changes are backward compatible
--------------------------------------------------------------------------

Thanks for your help!

Comienza comparando las especificaciones old.json y new.json adjuntas y, a continuación, rastrea el manejo del cambio de nombre de securitySchemes apiKey y de la opción incompatible.security.scheme.scheme.change. La corrección debe informar de la ruta, el campo y los valores antiguo y nuevo modificados, permitiendo a la vez deshabilitar esa regla; verifica que el registro de cambios de la API refleje estos detalles.