feat(wdl-analysis)!: incremental analysis

[Serial-ATA]

Previously, any analysis request on a document would:

1. Start from scratch
2. Unconditionally invalidate all dependents

That made working with the LSP in large workspaces heavier than necessary.

This adds a new per-document AnalysisCache that gets populated with all items and a graph of their dependencies on the first pass, then incrementally edited on any later analysis requests.

The cache works off two layers of hashes: SignatureHash (name+inputs+outputs) and BodyHash (any body statements)

In the local document, a difference in either hash will mark the item as dirty. For imports, only SignatureHash differences are significant.

For example:

# greet.wdl
version 1.3

task say_hello {
    input {
        String name
    }

    command <<<
        echo "Hello, ~{name}!"
    >>>

    output {
        String greeting = read_string(stdout())
    }
}

# main.wdl
version 1.3

import "greet.wdl"

# `do_say_hello` depends on the "greet.wdl" import
workflow do_say_hello {
    call greet.say_hello { name = "John" }
}

Changing the signature of greet.say_hello would invalidate:

• greet.say_hello
• The "greet.wdl" import
• main.do_say_hello

However, changing the body of greet.say_hello will only ever invalidate greet.say_hello.

Note that this is only incremental analysis. Each analysis request will still do a full validation pass.

Before submitting this PR, please make sure:

For external contributors:

• You have read the contributing guide in its entirety.
• You have not used AI on any parts of this pull request.
• You have added a few sentences describing the PR here.
• Your code builds clean without any errors or warnings.

For all contributors:

• You have added tests (when appropriate).
• You have added an entry in the CHANGELOG (when appropriate).
• You have updated the README or other documentation to account for these changes (when appropriate).
• You have made a PR to the next branch in the sprocket.bio repository (when appropriate).

For PRs containing lint rule changes:

• You have updated any and all effected entries within RULES.md.
• You have added a test case in crates/wdl-lint/tests/lints that covers every
  possible diagnostic emitted for the rule within the file where the rule
  is implemented.

[claymcleod]

The thing I would most like to see added is a test that analyses a fixture cold, applies an edit sequence, and then asserts the result matches a fresh analysis of the same final text, because every defect I have commented on would have been caught by one and without it the design stays one unhashed field away from silent staleness. This also needs a rebase before it can land, since main has rewritten except_directive_valid.rs in the meantime.