[Do not merge] Experimenting hook integration within kedro core

[ravi-kumar-pilla]

Description

As part of spike - #5161

Development notes

• Integrate hook registration within Kedro session
• The hook class can be implemented as a plugin - https://github.com/kedro-org/kedro-plugins/tree/test/validator/kedro-validator
• Explored other options of having the logic within session.py or a new class like KedroValidator in a utils or validator.py file. The hook registration way seems cleaner but might have some drawbacks considering how hooks work with parallel runner.

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