Check for using ref's instead moving values in wt public interface

[pathscale]

Migrated from pathscale/wt-dead#108. Originally opened by @Handy-caT on 2025-08-13T14:31:37Z.

[pathscale]

Valid pre-1.0 API audit. Generated select/delete methods use owned generic conversion through PrimaryKey: From; this is convenient for Copy keys and some borrowed strings, but tuple/custom keys and row mutations can still force ownership or clones. Acceptance should inventory every public generated method, adopt Borrow or reference forms where sound, and add compile tests for String, tuple, and custom primary keys. Otherwise explicitly freeze the owned 1.0 API.

[pathscale]

Confirmed still open with compile probes on the current PR #46 merge ref. select(&String) fails because the generated primary key implements From<String> but not From<&String>; select(&(String, String)) fails for the same reason on tuple keys. The owned API remains and the pre-1.0 decision is still required.

[pathscale]

Resolved by #47. Generated primary keys now accept borrowed generated keys, raw single keys, &str for String keys, and borrowed composite tuples. Tests cover String/&str, tuple, generated-key, and custom-key inputs across select, range, update, in-place update, and delete paths.