change owner to project for image commands

[Steve Martinelli]

Image create and set taken an "owner" argument, which is the same as the keystone "project". These should be changed to `project`, and accepted silently for a full year. Image list also uses the "Owner" column header, which will be changed over. If changed over permanently, this is backwards incompatible, and should be listed in OSC docs.

Reno notes should be created to highlight the deprecation and silent acceptance of "owner", as well as the change in the list command.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/264684

[OpenStack Infra (hudson-openstack)]

Change abandoned by Jude Augustine Job (<email address hidden>) on branch: master
Review: https://review.openstack.org/264684

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/259595
Committed: https://git.openstack.org/cgit/openstack/python-openstackclient/commit/?id=cf2de9af79cedd51ca080f5a6521997c05647418
Submitter: Jenkins
Branch: master

commit cf2de9af79cedd51ca080f5a6521997c05647418
Author: Dean Troyer <email address hidden>
Date: Fri Dec 18 14:16:45 2015 -0600

    Change --owner to --project in image commands

    * image create and image set now use --project to specify an alternate
      project to own the image
    * --owner is still silently accepted but deprecated, add warning messages
    * --project and --owner are mutually exclusive to prevent precedence issues

    Closes Bug: 1527833
    Change-Id: Iccb1a1d9175ef9b5edcd79d294607db12641c1f0