Catalog to config

[ElenaKhaustova]

Description

Made on top of https://github.com/kedro-org/kedro/pull/4347 (review it first)

Implementation of https://github.com/kedro-org/kedro/issues/4329

Full context: https://github.com/kedro-org/kedro/issues/3932#issuecomment-2474006376

TODO:

• [x] Exclude parameters
• [x] Add docstrings and release notes
• [x] Open related tickets:
  • https://github.com/kedro-org/kedro/issues/4327, PR: https://github.com/kedro-org/kedro/pull/4347
  • https://github.com/kedro-org/kedro/issues/4326
  • tickets for datasets required extending parent AbstractDataset.to_config(): https://github.com/kedro-org/kedro-plugins/issues/950

Development notes

To run pytest tests/io/test_kedro_data_catalog.py::TestKedroDataCatalog::TestKedroDataCatalogFromConfig or see an example from How to test section in #4329

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

[ElenaKhaustova]

Is it worth splitting the version validation PR separately? Or is it tied to the "catalog to config" prototype in any way?

https://github.com/kedro-org/kedro/pull/4347