fix(typed-link): scope inline Dataview fields to their bracket span

[michaelpporter]

Refs #731 — intentionally not an auto-closing keyword; the issue is closed when the fix ships in a release.

Problem

Pass 2 of the typed_link builder (body inline fields) worked at line granularity: it asked "does this line open with an inline field?" and then attributed every link on that line to it.

So (down:: [[y]]) [[x]] in x.md made both [[y]] and [[x]] down children — including a self-loop from the note to itself.

Fix

parse_inline_field (name only) becomes parse_inline_fields, which returns every field on the line plus the character span its value occupies, following Dataview's actual grammar:

• Wrapped — (down:: …) / [down:: …] anywhere on the line; the value ends at the matching close bracket.
• Bare — down:: … at line start (optionally after a list marker); the value runs to end of line, unchanged.

Links are then assigned by column, and a link falling outside every span produces no edge.

find_close_bracket counts depth of only the opening bracket's own type, so nested wikilinks ([down:: [[X]]]) and markdown links ((down:: [y](y.md))) close correctly. An unclosed wrapper falls back to end-of-line.

Behaviour change

Prose links merely near an inline field no longer create edges. That's the correct Dataview reading, but a vault relying on (down:: [[y]]) [[x]] linking both would now need down:: [[y]] [[x]].

Tests

bun run build && bun run test pass. The existing mock gave every link col: 0, which the old code never read — mock_file's links now takes an optional col (defaulting to 0, so list_note tests are unaffected), and a scan_links helper derives real columns from the body text so builder tests mirror what Obsidian's cache supplies.

New cases: the #731 repro, link-before-field, two wrapped fields on one line, bare field still claiming the whole line, multi-line bodies, and span assertions for nested/unclosed brackets.