Performance tests for `DataCatalog`

[ankatiyar]

Description

Partially resolve #4125

Development notes

Added performance tests for DataCatalog I'm wondering if it's worth adding them for KedroDataCatalog as well, since the interface is still in active development? Ignore benchmark_ocl.py since that is under review in #4225

To run locally: asv run or asv run --quick

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]

Could we wait until we merge https://github.com/kedro-org/kedro/pull/4218 for KedroDataCatalog? After that, the interface won't change much, so it might be easier. So I would bound this PR with the old catalog only, but up to the developer.