API Design Update Including YAMLs

[TarekAbouChakra]

API Design Changes:

• Default Searchers as YAML Files: Users manually select NePS YAML files at neps.run.
• Automatic Searcher Assignment: Users can skip selection, and NEPS assigns a searcher based on the search space.
• Custom Searcher YAML Files: Users can create and link their custom searcher YAML files using searcher_path in neps.run.
• Prioritizing kwargs: Users can still add kwargs to neps.run, which take precedence over YAML configurations.
• Limitation on Changing kwargs: Changing kwargs is allowed only when the user specifies a searcher.

Extras:

• Replicated Searchers in __init__ having SearcherMapping: Except for cost_cooling searcher.
• README File: Added detailed instructions.
• SearchConfigs Class: Provides insights about default NEPS searchers (algorithm, searcher names, kwargs...).

Minor Issue:

• Initially, sample_default_first was intended to be True when using priors, but it failed when having neps.FunctionParameter in the search space. It should now be set manually.

[TarekAbouChakra]

In the latest push:

• Fixed some minor bugs.
• Added a new 'optimizer_info.yaml' file that saves essential information in the optimization directory such as the optimizer's name, algorithm, whether it's user-defined (a boolean), and whether any arguments were accepted (another boolean).
• Created test cases to validate optimizer's proper functioning. (TODO: still need to add a test case for when the searcher is designed by the user and a searcher_path is passed)

[TarekAbouChakra]

Latest push:

• Creating a new marker for the yaml_api test case
• Testing only done locally for the yaml_api

[Neeratyoy]

Do we have a neps utility that given a folder can return a status whether runs have started, failed, ended, etc.? Maybe that is for a future PR.

Nevertheless, can we assert and check somehow whether the runs were successful?
Asserting if the kwargs were correctly updated or the right algorithm was called. Simple, sanity checks.

[TarekAbouChakra]

Working on status thing for a future push as we discussed.

Asserting is now included in the metahyper, checks the algorithm and simply if any kwargs were updates.