fix(admin)!: require all create-security body params

[johnpmitsch]

Summary

The POST /endpoints/:id/security/* create endpoints reject requests with a 400 when a required body param is missing or blank. This makes those params required in the SDK's typed surface so callers get a compile/type error up front instead of a server-side rejection. It extends the same fix already applied to create_jwt's kid.

Required fields, now non-optional across core + all bindings:

Endpoint	Required param
create_referrer	referrer
create_ip	ip
create_jwt	public_key, name (plus kid, already required)
create_request_filter	method (array)

create_token is unchanged (the token is server-generated).

This is a breaking change to the typed signatures (fix(admin)!). No client-side empty-string/empty-array validation is added; the server remains the source of truth for blank values.

Per-binding mechanics follow the existing kid precedent:

• core: Option<String> -> String, Option<Vec<String>> -> Vec<String>
• python: positional required args (no None defaults); stubs regenerated
• node: required struct fields; index.d.ts regenerated
• ruby: hash_require_string / hash_require_vec_string; RBS sigs updated
• examples and all four per-language READMEs updated

Test plan

• cargo check (all crates) and just lint pass
• cargo test -p quicknode-sdk --lib — 211 passed
• Rust example compiles (--features rust)
• just python-build, just node-build, just ruby-build all pass; regenerated .pyi and index.d.ts show the params as required

Closes DX-5868