llms.txt: config-schema Required column is a pointer-kind guess (from #2608 review)

Non-blocking M3 from the #2608 review. `cmd/conduit/internal/llmsgen/configschema.go:122` sets `Required = f.Type.Kind() != reflect.Pointer`, so every non-pointer config field (name, status, description, …) renders `Required: yes` in llms-full.txt. Requiredness isn't encoded in these structs (no validate tag) — it's enforced by config validation — so this mislabels optional fields as required, which is actively misleading for the agent-facing reference. Fix: drop the Required column for the config structs (keep it for connector params, which use real `config.ValidationTypeRequired`), or relabel/caveat it. Connector-param requiredness (connectors.go isRequired) is correct and unaffected.

Start at cmd/conduit/internal/llmsgen/configschema.go:122 and inspect how config structs produce the Required column in llms-full.txt. Compare that behavior with connector-param requiredness in connectors.go, especially isRequired. Done means config fields are no longer misleadingly marked required while connector-param requiredness remains unchanged.

Written by the indexing model from the issue text.