Allow parsing of unordered yaml

[ejseqera]

Right now, we expect that the user is configuring the yaml to be in the order of the resources created. So for example, you will create an organization -> workspace -> teams -> credentials -> compute-envs -> etc. This mirrors the typical workflow you would follow on the UI.

However, if you add compute-envs before credentials, this will throw an error as the compute-envs add method will inherit the credentials as a CLI argument.

We can make this dummy proof to specify a hierarchy when parsing the yaml and running the methods. Something to look to do in the next version.

[ejseqera]

Implemented in #57.