[Bug]: check-config-migration-metadata fails on specific case

[guillaumerochelle]

Package name

components

Package version

11.3.4

Reproduction steps

There seem to be a bug in the builder check-config-migration-metadata.
Let's suppose you have metadata for a configuration interface with no properties:

[
  {
    "library": "@lib/components",
    "name": "MyConfig",
    "path": "packages/@lib/components/configuration.ts"
    "runtime": true,
    "type": "APPLICATION",
    "properties": []
  }
]

If a property is added to MyConfig, the metadata becomes:

[
  {
    "library": "@lib/components",
    "name": "MyConfig",
    "path": "packages/@lib/components/configuration.ts"
    "runtime": true,
    "type": "APPLICATION",
    "properties": [
      {
        "description": "My image path",
        "label": "Image path",
        "name": "imagePath",
        "type": "string",
        "value": "img/path/name.jpg"
      }
    ]
  }
]

Current result

The metadata-checks builder will throw an error mentioning that:
Property @lib/components#MyConfig has been modified but is not documented in the migration document.

To be able to pass the check, we need to document that the config has been deleted, which isn't correct.

{
  "version": "1.0.0",
  "changes": [
    {
      "contentType": "CONFIG",
      "before": {
        "libraryName": "@lib/components"
        "configName": "MyConfig"
      }
    }
  ]
}

Expected result

A new property has been added so nothing should be documented.

Additional comments

No response

[matthieu-crouzet]

We should also filter configuration without properties from the metadata