Add kedro catalog rank command

[AhdraMeraliQB]

Takes over #2796

Description

This PR introduces the command kedro catalog rank which ranks all dataset factories in the catalog config in the order of how they are matched (i.e. if an explicitly named dataset could match several of the factories in the catalog, it would be resolved with the first on the list.)

The priority is determined as such:

1. Decreasing specificity (number of characters outside the curly brackets)
2. Decreasing number of placeholders (number of curly bracket pairs)
3. Alphabetically

Added note on streamlining the terminology

It looks like dataset factory is equiv to factory pattern, catalog factory, dataset pattern, dataset factory pattern and others that have been used interchangeably. As per #2670 any mentions of a catalog entry that makes use of placeholders will be referred to as a dataset factory. Catalog factories refer to all dataset factories within a specific catalog.

What this means in practice / Why this is useful

As seen in the test case, a catalog is created with the following patterns:

1. an_example_{place}_{holder},
2. an_example_{placeholder},
3. an_{example_placeholder},
4. on_{example_placeholder},

The explicitly declared an_example_data_set could match any of patterns 1, 2, or 3: an_example_{data}_{set}, an_example_{data_set}, an_{example_data_set}. Priority matching means that it will be resolved with the first pattern.
kedro catalog factories allows users to confirm the order in which factory patterns are considered for matching.

Checklist

• Read the contributing guidelines
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added a description of this change in the RELEASE.md file
• Added tests to cover my changes

[ankatiyar]

I also think we should add these CLI commands to the dataset factories docs too (https://docs.kedro.org/en/latest/data/data_catalog.html#load-multiple-datasets-with-similar-configuration-using-dataset-factories) but that can be done after kedro catalog resolve. Tested the implementation, all good! :)

[ankatiyar]

Looks great! ⭐

[merelcht]

Were the changes in test_cli not necessary anymore? https://github.com/kedro-org/kedro/pull/2796/files

[AhdraMeraliQB]

@merelcht

Were the changes in test_cli not necessary anymore? https://github.com/kedro-org/kedro/pull/2796/files

Without exceeding a command depth of three words the changes are no longer necessary. I didn't include them here as I was unsure if there would be any effect on kedro-telemetry. I think the correct action here would be to resolve this duplication instead of refactoring the test on framework-side, when the code itself isn't used.

[merelcht]

Were the changes in test_cli not necessary anymore? https://github.com/kedro-org/kedro/pull/2796/files

Without exceeding a command depth of three words the changes are no longer necessary. I didn't include them here as I was unsure if there would be any effect on kedro-telemetry. I think the correct action here would be to resolve this duplication instead of refactoring the test on framework-side, when the code itself isn't used.

Got it! Totally agree that we should remove the duplicated code instead, but of course as part of another PR.

[merelcht]

Great work! Thanks for also updating the docs in this PR ⭐