Description of problem:
It seems in 6.4 something changed to make Virt-who configuration objects tied to organizations, such that it is now required to specify the organization when using 'hammer virt-who-config deploy'

Version-Release number of selected component (if applicable): 6.4


How reproducible: Always


Steps to Reproduce: 
1. Create an organization (other then the default)  call virt-who-config
2. Create a virt-who config using the Satellite virt-who config plugin
3. Copy the deployment command to the clipboard and run it on satellite.


Actual results:
-bash-4.2# hammer virt-who-config deploy --id 1
Could not deploy the Virt Who configuration:
  Resource config not found by id '1'
-bash-4.2#

Adding the organization id (ie hammer 'virt-who-config deploy --id 1 --organization-id 5') makes it work.

Expected results:
Either the command doesn't require the organization to be specified or the command in the "deploy" tab includes the organization

Additional info:
In 6.3 there was no requirement to specify the organization, is this a new requirement in 6.4? If so we need to update the command we are having people copy.