[DataCatalog2.0]: Move pattern resolution logic to the separate component

[ElenaKhaustova]

Description

Solves #4110

Relates to #3925

Please see the suggested order of work in this comment

Development notes

This PR includes the following:

1. Moving pattern resolution logic to a separate component - CatalogConfigResolver
2. Updating DataCatalog to use CatalogConfigResolver internally
3. Some refactoring to make kedro run command and kedro catalog commands work after the catalog updates
4. DataCatalog interface remains the same, so no breaking changes introduced

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

• Read the contributing guidelines
• Signed off each commit with a Developer Certificate of Origin (DCO)
• 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
• Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

[idanov]

Not a big fan of continue since it harms the flow of thinking while reading the code. Could we do this instead:

for ds_name in (pipeline_datasets - explicit_datasets - filter(is_parameter, pipeline_datasets)):

[ElenaKhaustova]

We will have to do this since explicit_datasets is a dictionary:

for ds_name in (pipeline_datasets - set(explicit_datasets.keys()) - filter(is_parameter, pipeline_datasets)):

and for me, it looks way more complex to understand than

for ds_name in pipeline_datasets:
    if ds_name in explicit_datasets or is_parameter(ds_name):
        continue

It's also slightly worse from the complexity point of view though I agree both cost nothing.

Curious what other think.

[merelcht]

This is looking really good @ElenaKhaustova ! I love the separation of dataset factoreis resolution logic from the catalog ⭐

I left some comments and questions, mostly around naming/positioning.

[merelcht]

Thanks for addressing my comments @ElenaKhaustova, I don't have any blocking remarks anymore. Don't forget to add this change to the release notes!

[ankatiyar]

Great work @ElenaKhaustova ⭐ 👏🏾 💯
Left a small comment but looks good!

[astrojuanlu]

I see that there are no changes in DataCatalog.from_config, only in DataCatalog.__init__ (rarely used in interactive contexts) and so my understanding is that this has zero user impact 👍🏼

[idanov]

👍