Standardize arguments w.r.t. other BIDS Apps

[tsalo]

Summary

Many of the BABS parameters, such as --where_project, are kind of clunky and nonstandard across other packages, like datalad or BIDS Apps.

[tsalo]

• --input (babs init) --> --datasets, based on XCP-D, QSIPrep, etc. We can also change the pattern from <name> <path> to <name>=<path> to match how those BIDS Apps work.
• --list_sub_file (babs init) --> I'm not sure what the name should be, but it seems like we should be accepting a participants TSV file with participant_id and session_id instead of a CSV with sub_id and ses_id.
• --container_ds and --container_name (babs init) --> --container. We have --input set up as pairs of names and paths, so it seems weird to not do that with the containers too. I'd have it as --container <name>=<path>.
• --container_config_yaml_file (babs init, babs-status) --> --config.
• --type_session (babs init) --> --dataset-type
• --type_system (babs init) --> --queue to match Heudiconv
• --job_account (babs status) --> I don't know, but this one's confusingly named.

[tsalo]

Per @mattcieslak instead of --config, do --container-config.