Filter and list tests by full name and source line

Summary

Add native GocciaTestRunner selection and discovery controls for full test names and source declaration lines.

Why

Developers currently have to edit tests with .only or run an entire file to focus a failure. Name, line, and listing controls provide a safe one-shot workflow for editor integrations and local debugging.

Current behavior

The testing library can construct hierarchical full names, but registered test cases do not retain source locations. The runner accepts files/directories and executes every selected file; it has no name pattern, file:line, or list-only mode.

Expected behavior

• Add a full-name pattern filter, using a documented and consistent match rule.
• Accept a test file plus declaration line and select the test or suite registered at that location.
• Add a list-only mode with human-readable and structured JSON output.
• Preserve full suite ancestry in names and report a clear result when no test matches.
• Produce equivalent selections in interpreter and bytecode modes, including multifile inputs and --jobs runs.

Scope notes

• Store common registration metadata rather than parsing test source text in the CLI.
• The bytecode and interpreter callback representations expose source data differently; the registration surface needs one mode-independent location model.
• Test tags, projects/workspaces, changed/related selection, and watch mode are separate concerns and out of scope.
• This does not replace local .only; it provides a runner-native alternative.

Start with GocciaTestRunner and trace test registration into the interpreter and bytecode callback representations. Define the shared source-location and full-name selection flow, then verify name, file:line, list-only, no-match, multifile, and --jobs behavior in both execution modes.