[data processing] Order of "launch" buttons on jobs panel is suboptimal

[Chad Roberts]

As discussed at summit:

On the data processing/jobs panel, the first "launch" button is "Launch on New Cluster". Ideally, "Launch on Existing Cluster" would be the first button since it is most likely to be the most used option. "Launch on New Cluster" should be moved down on the list.

Bonus: When "Launch On Existing Cluster" becomes the default option, the "down arrow" to expand the action choices wraps down to the next line and looks horrible. It looks like the .actions_column is set to be 200px. It is debateable on whether we should try to override that number on our page, or maybe change the value, or perhaps we need to find shorter text to use in this place.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/140734
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=b5f53d679b41e2218112f2f62beb00b23f51a632
Submitter: Jenkins
Branch: master

commit b5f53d679b41e2218112f2f62beb00b23f51a632
Author: nikunj2512 <email address hidden>
Date: Wed Dec 10 20:57:05 2014 +0530

    Fixes the Order of "launch" buttons on jobs panel

    On the data processing/jobs panel, the first "launch" button is "Launch
    on New Cluster". This patch make the "Launch on Existing Cluster" as
    the first button. "Launch on New Cluster" is moved down on the list.

    Also when "Launch On Existing Cluster" becomes the default option, the
    "down arrow" to expand the action choices wraps down to the next line.
    So added css to fix this issue.

    Change-Id: I6f29e673f7ecf0316e855a3c0c0176d3c081491c
    Closes-bug: #1390362