[DataCatalog2.0]: KedroDataCatalog with dict interface

[ElenaKhaustova]

Description

Solves #4175

Development notes

See #4175 (comment)

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

[merelcht]

This looks very neat! I think after this change it might be a good moment to add some documentation about using KedroDataCatalog. Of course, we'll make it clear it's still in "beta", but I think this will help the team itself get familiar with it and it's behaviour.

[ElenaKhaustova]

After initial feedback on the interface we removed regex_search argument from keys(), values() and items() as it differs from the standard dict interface and looked not intuitive to users. We added filter() method instead for compatibility with the old list() method.

[idanov]

While I am usually in favour of simpler names, here filter is a bit ambiguous, since it's unclear what we are filtering exactly. If we are to keep a separate method, I'd rather keep list() with the regex.

[ElenaKhaustova]

Done

[Galileo-Galilei]

I quite disagree with this one, because list() already existed in previous version and virtually no one new about it being able to filter with regex as shown in the interview, so I'd argue that's not helping discovery.

I personally find filter more explicit, or even the original .values(regex=...). What do other think?
@astrojuanlu @noklam

[idanov]

Suggested change

	return list(self.__iter__())
	return list(self)

Would this work?

[ElenaKhaustova]

I made it for iteration cases, like

    def values(self) -> List[AbstractDataset]:  # noqa: UP006
        return [self._datasets[key] for key in self]