feat(c-abi): expose warmup_period / is_ready across the C ABI bindings (#297)

* feat(c-abi): expose warmup_period / is_ready across the C ABI bindings

The C ABI hub exposed new/update/batch/reset/free per indicator but not the
Indicator::warmup_period / is_ready queries that the native (Python/Node/WASM)
bindings already had, so C/C#/Go/Java/R callers could not ask an indicator
whether it was warmed up without feeding it and watching for NaN.

Regenerated from the ScriptHelpers capi + language generators:
- bindings/c: wickra_<ind>_warmup_period (size_t) and wickra_<ind>_is_ready
  (bool) for every indicator (504; the 10 alt-chart bar builders are excluded
  by design). wickra.h regenerated via cbindgen (additive only).
- bindings/csharp: int WarmupPeriod() / bool IsReady() on each wrapper.
- bindings/go: WarmupPeriod() int / IsReady() bool.
- bindings/java: int warmupPeriod() / boolean isReady().
- bindings/r: C glue + registration; hand-written warmup_period() / is_ready()
  S3 generics in methods.R, plus NAMESPACE exports.

Tests: C-ABI Rust unit tests, the C examples/archetypes.c suite, and the C#,
Go, Java and R archetype suites all gain a warmup/is_ready transition check.

* build(go): sync vendored wickra.h with the C ABI header

The Go binding vendors bindings/c/include/wickra.h; refresh it with the new
warmup_period / is_ready declarations so the CI sync check passes.

bindings/csharp/Wickra.Tests/ArchetypeTests.cs

@@ -34,6 +34,21 @@ public class ArchetypeTests
         Assert.InRange(last, 1.0, 10.0);
     }
 
+    [Fact]
+    public void Query_WarmupPeriodAndIsReady()
+    {
+        using var sma = new Sma(3);
+        Assert.Equal(3, sma.WarmupPeriod());
+        Assert.False(sma.IsReady());
+        sma.Update(1.0);
+        sma.Update(2.0);
+        Assert.False(sma.IsReady());
+        sma.Update(3.0);
+        Assert.True(sma.IsReady());
+        sma.Reset();
+        Assert.False(sma.IsReady());
+    }
+
     [Fact]
     public void Candle_Atr_IsFinitePositive()
     {