v1.25.0

Dry run for the schema tools (v1.25.0) (#17)

* Add a dry run to the schema tools

table_*, column_*, view_* and role_* writes take dryRun: true. A call-tool
filter opens a DryRun scope (AsyncLocal) around the tool; inside it,
DataverseHttpClient records every POST/PATCH/PUT/DELETE instead of sending it
and answers with an empty 204, while GETs still go out. The result lists the
planned requests with URL, relevant headers and the exact body, plus the
tool's own output.

The production guard lets dry-run calls through, including the tools that
had their own validate-and-report dry run before (workflow_set_definition,
bpf_set_definition, solution_uninstall, whose dry run is the default). Those
keep their behaviour; the generic filter only wraps tools whose dryRun
parameter carries the generic description. The refusal message points to
dryRun.

Verified live against a sandbox: a dry-run table update sent only the GET of
the definition and recorded one PUT with the full merged body.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J4JSCheFvAEVCZLUQ29Uqj

* Document the dry run (v1.25.0)

README security table and comparison, modeling-patterns skill: when to use
dryRun and what a production refusal means.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J4JSCheFvAEVCZLUQ29Uqj

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>