Support negative line numbers for goto

[barkure]

Summary

Implements the request from #684.

• Support negative line numbers for file goto targets, e.g. edit README.md:-1 opens at the last line and edit README.md:-5 opens at the fifth line from the end.
• Apply the same negative line behavior to the interactive Go To dialog, so CLI and in-editor navigation stay consistent.
• Keep columns positive-only; values like README.md:10:-5 are not treated as goto targets.

Test plan

• Built successfully with:

cargo build -p edit --release

• Ran parser coverage with:

cargo test -p edit documents::tests::test_parse_last_numbers

• Manually tested:
  target/release/edit README.md:-1
  target/release/edit README.md:-5

[lhecker]

To me it seems unnecessary to introduce a new type just to wrap a single if condition in a function. It should be fine to keep using Point and just move the if/else into the code below.

John Carmack wrote many years ago "If a function is only called from a single place, consider inlining it." It is as true as it has ever been.

[barkure]

Updated as suggested — removed GotoTarget and kept using Point, with the line resolution inlined at the call sites.