Filter out subworkflow invocations

[mvdbeek]

I think users don't need to see their nested invocations from the main invocation list. If needed they can be found through the invocation steps. The only exception we're making is that we show subworkflow invocations if filtering for a specific workflow id.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.