project o difficult to configure with security token auth

First, I really love the new project o interface! But I did run into one bump when using security token auth.

When starting with project o, the CLI tells me to run o <my-tenancy-ocid>. Since I was using security token auth, it mirrored this OCI CLI warning:

WARNING: The active profile contains a value for 'security_token_file' which is not being used. To authenticate using the token, specify --auth security_token

However the following does not work:

o <my-tenancy-ocid> --auth security_token

Because the setup_ocids_file function only works with exactly one argument, and it doesn't pass along options.

This makes the tool unusable if your main use case is security token auth. I was able to get by with a workaround by running the special commands individually:

o iam compartment get -c <my-tenancy-ocid> --auth security_token go
o iam ad list -c <my-tenancy-ocid> --auth security_token go
o iam region list --auth security_token go
o iam compartment list -c <my-tenancy-ocid> -ciis true -all --auth security_token go

If options could be passed along appropriately, the onboarding with security token auth would be much easier.

Start at the setup_ocids_file function and reproduce the onboarding command with --auth security_token. Trace how the CLI handles the listed IAM and region commands when options are supplied, then ensure the onboarding path passes those options through. Done means the documented command works with security token authentication.