fix(csharp-parser): mark parameters with a default value as optional
C# main parameters with a default value (e.g. Main(string s = "hi")) were emitted with has_default = false even though the default was parsed, so the inferred schema marked them as required — the auto-generated form shows the field as mandatory, and strict schema validation rejects webhook/API calls that omit the optional argument.
This makes C# the only parser that could emit default: Some(...) and has_default: false on the same Arg, which is self-contradictory. The parsers for languages that do have default values derive the flag from the parsed default — php, bash, yaml and java all use default.is_some(); go and rust hardcode false, but they pair it with default: None, since neither language has default parameter values. C# parses the default and then ignored it. This derives it the same way the others do. Added assertions to the existing test_parse_csharp_sig pinning default + has_default for a defaulted parameter and two required ones.
Summary by cubic
C# main parameters with a default value are now marked as optional, and omitted arguments get their declared default at runtime instead of default(T).
C# arguments were emitted with has_default = false even when a default was parsed, so schemas and forms treated them as required and rejected calls omitting them. The parser now derives has_default from whether a default was parsed, consistent with other language parsers.
The generated C# wrapper reads omitted arguments' declared defaults from the compiled Main method by parameter name, so defaults like Main(int n = SomeConst) work even when the default expression isn't a JSON literal, and params arrays don't break the lookup. Verbatim @-named arguments bind via a JsonPropertyName attribute since @ isn't part of the serializer-facing name. A test covers defaulted and explicitly-null arguments. The cache key includes a wrapper version so binaries built with the old wrapper are rebuilt.