Details for collections should support projects, devices, as well as resolving vars

[Jim Baker]

$ craton-get 'v1/hosts?details=all&resolved-values=true'
{
  "errors": [
    "Additional properties are not allowed ('resolved-values' was unexpected)"
  ],
  "message": "Bad Request"
}

(craton-get is a wrapper around curl I use)

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/439175
Committed: https://git.openstack.org/cgit/openstack/craton/commit/?id=1d3fcad7863f4a5ae75c146eba4cf94e41cef81b
Submitter: Jenkins
Branch: master

commit 1d3fcad7863f4a5ae75c146eba4cf94e41cef81b
Author: sulochan acharya <email address hidden>
Date: Thu Mar 2 11:43:05 2017 +0000

    Allow resolved vars in details list calls

    Currently the details=all flag allows us to only
    get local variables. This changes that to be resolved
    variables such that it matches the rest of the variables
    calls.

    It also adds details calls to /clouds and /projects
    endpoints where it was missing.

    Closes Bug: 1667767

    Change-Id: Ia2de9110aa118c3fe7cd9374ceed2ce74f13c74e