fix: fix a debug! log which causes a panic.

[peterhuene]

The problem occurs when:

1. Logging with DEBUG level (i.e. -vv).
2. Using the TES backend.
3. Using inputs that are remote URLs.

There's a debug! log message in task evaluation that logs what inputs have been downloaded and mapped to.

The logging assumes that if the input is remote, it has been downloaded (i.e. localized).

But that's not the case with the TES backend; the input can be remote and not downloaded because task execution occurs remotely.

The fix is to properly add a match case to handle it.

Before submitting this PR, please make sure:

For external contributors:

• You have read the wdl crates' CONTRIBUTING guide in its entirety.
• You have not used AI on any parts of this pull request.

For all contributors:

• You have added a few sentences describing the PR here.
• You have added yourself or the appropriate individual as the assignee.
• You have added at least one relevant code reviewer to the PR.
• Your code builds clean without any errors or warnings.
• 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 either (a) made a PR to the next branch in the sprocket.bio repository [if you are a Sprocket team member] or (b) have suggested any changes you think need to be made to sprocket.bio in the description of your PR [if you are an external contributor].

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.