GitLab

symphony/client/simbricks/client/client: logic to follow run as part of client lib + rich formatting

symphony/orchestration + symphony/runtime: users can specify artifact paths on instantiation to create artifacts after simulation

symphony/utils/simbricks/utils/artifatcs : added funciton to later create artifatcs from user provided paths

cli/simbricks/cli/commands : commands for handling files associated with runs + handel creation, deletion, retrieval of runs

client/simbricks/client/client: functions for handling the creation, retrieval and deletion + updates of runs

cli/simbricks/cli/state: added admin client + turned functions into properties; cli/simbricks/cli/commands/admin: added admin commands

Also use pydantic-settings here for now. Add options for auth, and base
url.

Should be explicitly created by the runtime later and set.

Do not assume that everything is running from the repo. Finding things
relative to the python script paths is also broken once packages get
installed via pip etc. For now just default to having SimBricks under
/simbricks or else this has to be set in the environment.

This results in the same environment as with the provided dockerfiles.
Then we can use that as the default setting for the instantiation
environment.

`symphony-dev` sets up the current python environment for development.
Includes installing required dependencies and then editable installs for
each simbricks python package.

`symphony-build` build wheels and source packages for all simbricks
python packages in `symphony/dist/`.