Use LID fragment to access workflow output by name

[bentsherman]

• Rename WorkflowRun -> WorkflowLaunch
• Rename WorkflowOutput -> WorkflowRun
• Use the WorkflowRun in the nextflow lineage list command
• Remove TaskOutput since it is not used
• Remove #output as a shortcut to access task/workflow outputs
• Use LID fragment only to access workflow output by name
• Remove the use of URL query syntax

Some miscellaneous improvements I made along the way:

• Remove extraneous .meta subdirectory
• Remove unused properties from data model

[netlify]

✅ Deploy Preview for nextflow-docs-staging canceled.

Name	Link
🔨 Latest commit	4e29bb8
🔍 Latest deploy log	https://app.netlify.com/sites/nextflow-docs-staging/deploys/680c01187057840008ec5602

[bentsherman]

This PR removes a lot of unnecessary complexity around the LID filesystem that I feel is getting in the way of core use cases.

There are a few tests still failing, mainly because the view command now goes through LinPath instead of LinUtils.query() to resolve the LID, and it is currently trying to return the actual path of FileOutputs instead of the metadata description.