Make behaviour with OmegaConfLoader for kedro ipython consistent with "regular" CLI flow

[merelcht]

Description

When using the OmegaConfLoader with kedro ipython it behaves differently from running it through the CLI e.g. kedro run

Differences:

1. kedro ipython fails to start up while trying to load logging.yml this is a similar error that was solved in Only convert omegaconf DictConfig to primitive type for logging #2176 but because the flow is different for the ipython startup this needs to be fixed in another way
2. kedro ipython fails to start up when you have empty parameters files
3. You get different errors when trying to use environment variables in the catalog or parameter files. When executing kedro run you correctly get an error about oc.env not being supported, but when going through the ipython workflow it parses the environment variables correctly and would only fail if that value doesn't fit the catalog entry/parameter. (e.g. passing a AWS key as file path in the catalog)

[merelcht]

I couldn't figure out what was going on... created a new project.. nothing wrong 🤦‍♀️ Glad I found after starting at this for 1 day instead of more 😅