Fix workflow editor bug related state updates for collections attached to multiple input data parameters.
Detail bug report from Michael Crusoe here : https://trello.com/c/0mdGCx4P.

This also fixes a test case added in 289e48b which was both attempting to assert something wrong and was incorrectly implemented. Augmenting the workflow editor test suite with some actually valid test cases that assert the correct behaviors.

For a longer explaination - workflow input terminals have two related concepts 'canAccept' and 'attachable'. An output terminal is 'attachable' if in the abstract it could be attached to the input regardless of whether the input is already filled or not. 'canAccept' is more stateful in that an output terminal is 'canAccept'able if the input terminal is not filled ('_inputFilled') and it is 'attachable'.

So - the problem was 'attachable' was not correctly defined for a multiple input data parameters. 'attachable' was asserting that any connected input terminal could not be 'attachable' by an collection output terminal - so on these asynchronous node state changes collections attached to multiple input data parameters were being wiped out. The more percise/correct distinction is that if a multiple input data parameter has single inputs connected to it - it cannot also have a collection connected to it (yet anyway). This fixes the mentioned bug.

The problematic test case was conflating 'attachable' and 'canAccept'able - I have fixed the test case to verify the correct 'attachable' logic and added newer, higher level test cases to test the canAccept logic and the actual behavior the end user would observe (of the connector being destroy).
Pack scripts.
Make it possible to load dynamic job runner rules from somewhere other than galaxy.jobs.rules.
Test fixes for 5ce55f9; correct spaceghost.stderr to use system.stderr (thanks, John); correct api-workflow-tests (which I completely forgot *I* had made) and add test-data
missing import
ToolForm: Add sliders, radio buttons for boolean and integer fields, Ui: Update frames
Remove call to send_control_task that should not have been added to admin.package_tool in the first place.
Merge stable.
Small tweaks to some functional test tools.

Add data labels so the tools works in the workflow editor and added a conditional switches to some with collection params and multiple input data parameters to test some state-y logic in workflow editor.
Add functional test tool demonstrating/testing special parameters.
Add integration test tool demonstrating setting output dataset formats.

Directly setting format attribute, setting to format to 'input' (ambigious, non-deterministic and should be deprecated IMO), using format_source, and using change_format actions.
Add functional tool demonstrating/testing output filters.

Add new 'expect_num_outputs' attribute to 'test' element in tool XML to verify the produced number - needed to test output filtering.
PEP-8 fixes for tools/actions/__init__.py.
Unit test for galaxy.tools.action to ensure all datasets get same object store id.

Enables subsequent refactoring.
Small galaxy.tools.actions refactor related to object store...

Breaks up the big loop in execute a little bit but will enable a much bigger breakup in subsequent refactoring because the loop will no longer have to update the object_store_id local variable - that will be tracked in new object.
Refactor galaxy.tools.actions so can reuse functionality for creating job datasets.

(When creating datasets for explicit output collections.)
Unit tests for tool action code determining output formats.

With refactoring to reduce cyclomatic complexity. Also renaming 'input_ext' what it actually is 'random_input_ext'. We should fix that or at least issue a huge warning if we detect 'input' could have reasonable been different things.
Break up tool action loop refactoring filtering logic out.
Small optimization for implicit collection creation from tool execution.

Don't write out encode identifier, add to dict, and then reload object in dataset collection service - just pass through the object in the dictionary as is.
Refactor some collection-y tool methods ahead of collection outputs.

Tool mapping "structure" logic no longer assumes tool outputs are datasets - could also potentially handle logic related to structure of output collections as well now.

These variable names will make for sense down the road when tools that explicitly create collections exist and can be mapped over.