Consistent arg name handling

[CharanMann]

Currently some args names are optional and others are mandatory, refer below:

• No arg name for host: ./frodo logs tail -c idm-everything -l DEBUG openam-ps.forgeblocks.com
• No arg name for host, user, password, key, secret: ./frodo connections add https://openam-ps.forgeblocks.com/am john.doe@example.com passwordddddd keyyyyy secrettt

These args should be passed with arg names such as:

• ./frodo logs tail -c idm-everything -l DEBUG -h openam-ps.forgeblocks.com (No arg name for host)
• ./frodo connections add -h https://openam-ps.forgeblocks.com/am -u john.doe@example.com -p passwordddddd -k keyyyyy -s secrettt

This will avoid any confusion regarding these args handling

[vscheuber]

@CharanMann we introduced this behavior with rockcarver/frodo#6 "Refactor command options into arguments". We wanted to move away from using named params for mandatory params that had to be there always to cut back on number of characters to type. The commands I use now are streamlined like this:

frodo journey list volker The above command uses volker as the host argument and reads the connection profile and auto-populates the username and password arguments. The realm argument is using the determined default value depending on detected deployment type: /alpha for cloud, / for forgeops and classic.

For users using frodo every day, every character saved helps.

[atomicsamurai]

Testing slack integration.

[vscheuber]

Won't do. Re-open if you see a strong need to change our use of arguments and options.