Describe the bug
The CLI 2.0 no longer lets you push a package to a specific organization.
I rely on this feature often, so I had to roll my installed CLI back to 1.x

To Reproduce

• Have two organizations you work with (ORG1 and ORG2).
• Defaults are setup for ORG1
• Run: smartthings edge:drivers:package <path> -O <ORG2 ID>
  • OR: smartthings edge:drivers:package <path> -p <ORG2 profile from config.yaml>
• Now run: smartthings edge:drivers <either -O ORG2_ID or -p ORG2>
  • Also: smartthings edge:drivers <either -O or -p for ORG1, or let it default>
  • The driver will not be updated/published to ORG2, it will be on ORG1

Expected behavior
Using -O or -p ORG2 should send the package to the correct ORG2

Actual behavior
The driver is published to your default ORG1

Additional context

The help for edge:drivers:package no longer has -O as an option

The edge:drivers command does have -O and that command DOES work to see the drivers list on a separate Org.

I rolled back to 1.x and here is the help from the latest 1.x