deno test --doc: generated docs tests in JSDoc should it for naming (e.g. @example, token name, etc.)

[lowlighter]

Currently the @example JSdoc annotation can be used to title examples in generaed documentation.
(Example @std/fmt/bytes)

When using deno doc --test currently the name are auto-generated with the filename/lines, but for long files it makes it a bit cryptic to map them back easily.

A solution would be to use the @example value (if defined) to set the Deno.test name.
Eventually, the name of the token could be used too (e.g. the name of the documented function, variable, etc.)

vscode ➜ /workspaces/fmt/bytes $ deno test --allow-read --doc test.ts 
Check file:///workspaces/fmt/bytes/test.ts
Check file:///workspaces/fmt/bytes/test.ts$7-14.ts
Check file:///workspaces/fmt/bytes/test.ts$79-86.ts
Check file:///workspaces/fmt/bytes/test.ts$89-95.ts
Check file:///workspaces/fmt/bytes/test.ts$98-105.ts
Check file:///workspaces/fmt/bytes/test.ts$108-114.ts
running 0 tests from ./test.ts
running 1 test from ./test.ts$7-14.ts
file:///workspaces/fmt/bytes/test.ts$7-14.ts ... ok (0ms)
running 1 test from ./test.ts$79-86.ts
file:///workspaces/fmt/bytes/test.ts$79-86.ts format: Basic usage ... ok (0ms)
running 1 test from ./test.ts$89-95.ts
file:///workspaces/fmt/bytes/test.ts$89-95.ts format: Include bits representation ... ok (0ms)
running 1 test from ./test.ts$98-105.ts
file:///workspaces/fmt/bytes/test.ts$98-105.ts format: Include sign ... ok (0ms)
running 1 test from ./test.ts$108-114.ts
file:///workspaces/fmt/bytes/test.ts$108-114.ts format: Change locale ... ok (16ms)

Maybe also there may be no need to put the full file url, as the running X test from ./... is relative, it'd be less verbose to not be an absolute url/path but just a relative one