Feedback feature on configuration for v1.0 (network download and network directory should be connected)

[knaegle]

Is your feature request related to a problem? Please describe.
When I installed and configured the new version of KSTAR, there is leap that the configuration makes that isn't captured well in the documentation.
Current behavior:

1. I ran config.install_network_files(target_dir=<my_dir>)
2. I expected this should be setup and I didn't understand why config.check_configuration() reported issues
3. Once I tried running KSTAR it became clear to me that I needed to find the network structure made by the install_network_files and then navigate to the level directory to see what the import error matched.
4. I then manually added the path for pickle production running config.update_network_directory(<my_dir>)

Describe the solution you'd like
If someone installs network files then the update_network_directory should also be run as part of that so the installation and instantiation of the pickles and configuration directory is all done. Also, this should be detailed as part of the documentation (Getting Started).

[knaegle]

Adding additional clarity on this suggested feature.

The typical KSTAR user will not want to derive new networks and we want to make installation and configuration as seamless as possible. To this end, I am proposing that install_network_files should immediately run update_network_directory, so that complete configuration is done in a single step.

[srcrowl]

This has been fixed in the dev branch, but it still needs to push to main and pip/conda installs. Will close this once it is wrapped into the actual package