Allow ordering of service templates resource

[jntullo]

For the new ServiceTemplateTransformationPlan, ordering must happen directly on the service template. Currently, the API only allows ordering through a service catalog. It was discussed with @bzwei that ordering can be allowed in general for a service template, and no special case is needed for the new ServiceTemplateTransformationPlan since there is validation around whether a service template is "orderable".

Sample order without required fields:

POST /api/service_templates/:id
{
   "action": "order"
}

Sample order with required fields:

POST /api/service_templates/:id
{
   "action": "order",
   "required_field_1": "filled in field"
}

[abellotti]

let's rename to order_service_template

[abellotti]

let's add a test on the collection, ordering 2 templates. Thanks.

[abellotti]

don't we need the :validate_action option here too ?

[jntullo]

@abellotti it doesn't go on the collection, only on the resource, which is consistent with the other places we have it

[abellotti]

👍

[jntullo]

Now dependent on ManageIQ/manageiq#17023

[miq-bot]

Checked commit jntullo@06e955e with ruby 2.3.3, rubocop 0.52.0, haml-lint 0.20.0, and yamllint 1.10.0
4 files checked, 0 offenses detected
Everything looks fine. ⭐

[abellotti]

Thanks @jntullo for the update and enhancement. LGTM!! 👍

[simaishi]

Gaprindashvili backport details:

$ git log -1
commit c952f406381b13e463435946dd8a5d0f56a2ded5
Author: Alberto Bellotti <abellotti@users.noreply.github.com>
Date:   Tue Feb 20 09:59:34 2018 -0500

    Merge pull request #316 from jntullo/service_template_order
    
    Allow ordering of service templates resource
    (cherry picked from commit 2de9dcc3cb04c20f01bee57cbe8de6b7a8b0f4c8)