Make the Session more lightweight and re-entrant

[astrojuanlu]

At our organisation we often needed to run a kedro session from outside kedro, for example from streamlit app or a rest api. For now, we don't manage to do that, we instead run the web app server inside of kedro, more specifically inside a custom kedro runner. Here is our current reasons for doing that :

• We wanted to avoid creating and running kedro sessions in each HTTP request call. There is a lot of overhead included in the kedro session creation and session running (context creation, catalog creation, hooks, ...).
• We wanted to leverage kedro session, context and CLI as the main application lifecycle manager(entry point, config management,...)

@takikadiri at #2169 (comment)

This eventually resulted in https://github.com/takikadiri/kedro-boot/, see #2169 (comment)

The priorities are

• Enable data injection into KedroSession runs
• Make session_id customisable
• Make KedroSession re-entrant
• Understand API use cases

[astrojuanlu]

Added #3540 as sub-issue just so we don't lose sight of it! Ideally we can leverage part of that research