Describe the bug

Since #4648 (I expect, haven't confirmed) we can't name a cli session anymore with goose session -n name. It tries to resume a session and fails.

To Reproduce
Steps to reproduce the behavior:
goose session -n brand_new_name

produces

Error: No session found with name 'brand_new_name'

Expected behavior
We should be able to name sessions for 2 reasons:

• Avoid session name conflicts that prevents parallel goose usage. Previously the naming scheme was second based datestamp so that would fail if you created 2 sessions in the same second. Not sure if the new db approach makes this redundant
• Enables resuming named sessions.

Please provide following information:

• OS & Arch: osx
• Interface: CLI
• Version: HEAD (later than 1.9 release)