feat: add checkAfterItems in builders

[guillaumerochelle]

Proposed change

Add checkAfterItems in metadata-check builder.
This new option allows devs to deactivate checks on items set in "after" property.
This will allow documenting breaking changes in modules which don't have access to the complete metadata.

For example with this migration change:

{
  "version": "1.0.0",
  "changes": [
    {
      "contentType": "CONFIG",
      "before": {
        "libraryName": "@mylib/moduleA",
        "configName": "Foo",
        "propertyName": "bar"
      },
      "after": {
        "libraryName": "@mylib/moduleB",
        "configName": "Bar",
        "propertyName": "baz"
      }
    }
  ]
}

When running builder @o3r/components:check-config-migration-metadata, the metadata file is the one of module @mylib/moduleA and doesn't contain any metadata from other modules (@mylib/moduleB). The check for property "baz" in config interface @mylib/moduleB#Bar will fail.

With the new option checkAfterItems, we can deactivate this check.

Bonus: Add packageJsonEntry in the schema of :

• @o3r/components:check-config-migration-metadata
• @o3r/localization:check-localization-migration-metadata
• @o3r/styling:check-style-migration-metadata

Related issues

• No issue associated

[kpanot]

I am fine with the code but, if we follow the policy, a feature should be pull requested to the main branch.
We can do exception if the feature is mandatory to process properly to the main purpose of the tool (here the extractors).
It seems to be the case here but, as 11.3 is not the latest major, maybe you will need to move your target to release/11.4