fix(ocsf): emit schema-conformant OCSF events and honest downgrades

Native events failed the official OCSF 1.8.0 validator: device.os lacked
type_id, HTTP Activity emitted is_src_dst_assignment_known, sandbox
Process Activity events had no actor, connection_info lacked
direction_id, and SSH Activity events named no endpoint. Schema tests
missed these because they checked only top-level, non-profile
attributes. The 1.1 and 1.3 downgrade stripped three fields by name and
relabelled events that did not conform.

Add OS type and connection direction enums, require an actor on Process
Activity and an endpoint on SSH Activity at compile time, name the
supervisor's SSH server and domain endpoints with fields every version
accepts, and make schema validation recurse into nested objects, reject
undefined attributes, and honour declared profiles.

Make the downgrade schema-driven from definitions generated from the
vendored official 1.1.0 and 1.3.0 schemas: undefined attributes move
under unmapped.downgraded_attributes, unsupported profiles are dropped,
and an event is labelled with the target only when every requirement
holds, on the JSONL and OTLP export paths alike. Otherwise it stays at
native 1.8.0 and is counted by the gateway metrics
openshell_ocsf_log_kept_native_total and openshell_ocsf_otlp_kept_native_total
and a supervisor warning.

Keep it fixed with a Podman e2e test that validates the supervisor's
real JSONL, schemas compiled into test binaries so archived runs need no
source files, a production-like fallback context for producer tests, a
vendored-version guard, and documented schema update steps. Top-level
container stays unchanged pending a decision on #4283.

Closes #4283
Closes #4284

Signed-off-by: Adel Zaalouk <azaalouk@redhat.com>

Author: zanetworker