Removing KedroContext params and catalog hot-reload

[noklam]

Description

Remove the hot-reloading behaviour of params and catalog in favour of using the Ipython reload kedro magic. It will further clear up the responsibility of KedroContext as a dataclass, and the logic of creating them will be moved to session instead. by @idanov

Context

This work is part of the clean of up KedroContext, which was made into a dataclass in: #1465. KedroContext should merely be a container and not have any "advanced" logic or responsibility. Any instance creation etc. should be happening in KedroSession instead.

The hot-reloading of params and catalog is mainly useful for the interactive workflow, but reload kedro can achieve the same thing and so that should be the recommended way instead.

User problem

When users make changes in parameters.yml or catalog.yml and they're working in a Jupyter notebook, then they have to do %reload_kedro to see those changes reflected in their Jupyter notebook. This behaviour is not the same as when you run session.catalog in a notebook. We should make consistent.