Allowing declarations to be placed after other things of current scope

[TimSPb89]

An Issue

There are some scripts featured in production that use Declarations after Calls or other things of current scope. It causes pipeline-builder to throw an Error (Context initialization failed due to WDLParserError: Declarations are allowed only before other things of current scope).

This PR resolves this issue.

[coveralls]

Coverage increased (+0.4%) to 97.58% when pulling 7542e46 on fix_declarations-before-other-things-only into f2ee5de on dev.

[vpolyakov88]

PNG button doesn't work

22491d0
Steps to reproduce:

1. npm install
2. gulp serve
3. Open app in chrome
4. Click "To png" button

Expected result: picture of the scheme below is downloaded
Actua result: Nothing happens

Comments:
The same problem with any script scheme

[vpolyakov88]

Update

This behaviour is expected

Unexpected task name is displayed

22491d0
Steps to reproduce

1. npm install
2. gulp serve
3. Open app in chrome
4. Paste in "Paste your .wdl script here:" field a script that has an "if" pattern as follows: import "URL" as myImport.
5. Click "Build" button
6. Look at the "if" in the scheme

Expected result: "if" block has name "myOtherWorkflow"
Actua result: "if" block has name "workflow myImport.myOtherWorkflow as myOtherWorkflow"

Comments:
If the file is not imported the same situation does not occur.

You can observe it if use this script

[vpolyakov88]

[Fixed] Console error if user build script

8e9fb41
Steps:

1. run PB
2. open browser console
3. build attached script (link)
   exp.: the diagram is displayed
   act.: error in the console has appeared

app.js:67 Uncaught (in promise) Error: Context initialization failed due to WDLParserError: Undeclared call is referenced: 'normal_bam_and_bai' at app.js:67 at <anonymous>