Allow projects without a conf directory

Description

With hooks out, such as kedro-wings, I no longer NEED a conf directory, especially for small projects. For simple pipelines, it seems a bit much to have so many files and directories and deters users from starting small projects with kedro. I would love to build out a starter without a conf directory, but kedro throws the following error

ValueError: Given configuration path either does not exist or is not a valid directory: <my-directory>

Context

I think the ability to create very simple starters will yield an easier starting point for folks just getting into kedro. Currently, if we follow the kedro-pandas-iris starter format users need to touch at least three files to add new features (catalog, node, and pipeline). In my experience, this is so overwhelming for some that they step away and choose not to use the framework.

[Minyus]

I agree with @WaylonWalker . It would be more intuitive and reduce the learning cost for begineers to try Kedro if conf folder is optional rather than required.

[WaylonWalker]

I completely understand. This team has a much deeper understanding of a broader set of use cases and users than I do. I appreciate the consideration and feedback.