Publish option_skip to test item clients

[davidanthoff]

Forwards the skip keyword argument of @testitem through textDocument/publishTests.

JuliaWorkspaces records option_skip on TestItemDetail (julia-vscode/JuliaWorkspaces.jl#255, shipped in 12.0.0), but publish_tests dropped it. Without this the VS Code extension cannot see skip and so cannot forward it to TestItemControllers — a test item marked skip=true would silently run anyway.

Wire shape

optionSkip mirrors the JuliaWorkspaces type, Union{Bool,String}:

• false / true — a literal, known statically
• a string — the source text of an expression the test process evaluates immediately before the test item would run

Keeping the union rather than normalising to a string lets a client distinguish a test item that never runs (render it as skipped in the tree) from one whose outcome is only known at run time (run it and find out). The expression must be evaluated worker-side because it may inspect the worker's environment, e.g. VERSION < v"1.11" or Sys.iswindows(), which can differ from the language server's.

@dict_readable handles the union correctly — field_type collapses a non-Missing union to Any, so the value passes through unconverted. Verified both variants serialize to their natural JSON forms (boolean vs string) and round-trip through the generated Dict constructor.

Compat

Bumps JuliaWorkspaces to "12". Besides option_skip, 12.0.0 changes test item ids from positional (<uri>:<n>) to stable (<relpath>::<label>) — ids are forwarded verbatim here, so no change was needed in this repo for that.

Downstream

The VS Code extension needs a matching change to read optionSkip and forward it when creating a test run; TestItemControllers' json_protocol.jl gains the corresponding field in julia-testitems/TestItemControllers.jl#39.

🤖 Generated with Claude Code