draft: fix: align namespace model with F5 BNK 2.2 DPU docs

[bonnyr-f5]

Summary

Replaces the three-namespace model (f5-operator, f5-utils, bnk-gw) with F5 documented two-namespace model for BNK 2.2 FLO-based installs:

• f5-cne-core: FLO operator and CNE core components
• f5-bnk (configurable): CNEInstance, TMM, VLANs, NADs

Changes (15 files, 6 modules)

Module	Key changes
k8s/bnk-prerequisites	3 namespace vars to 2 (cne_core_namespace, cne_instance_namespace), 3 NS resources to 2, 3 FAR secrets to 2, outputs renamed, README rewritten
bnk/cneinstance	instance_namespace renamed to namespace (variable, main.tf refs, output, module.json wiring)
bnk/flo	module.json wiring: operator_namespace to cne_core_namespace
k8s/network-setup	Default f5-operator to f5-bnk, wiring updated
bnk/bnk-vlans	Default f5-operator to f5-bnk, wiring updated
bnk/bnk-gatewayclass	Default f5-operator to f5-cne-core

F5 Documentation Evidence

From clouddocs.f5.com BNK 2.2 Install using FLO:

• kubectl create namespace f5-cne-core
• helm install f5-lifecycle-operator ... --namespace f5-cne-core
• CNE_INSTANCE_NAMESPACE is user-configurable (example: f5-bnk-instance)

Coordinated merge required

Companion bnk-forge PR link will be added as a comment.

Additional fixes

• Fixed module.json default drifts in k8s/bnk-prerequisites

[bonnyr-f5]

Coordinated merge required

Companion bnk-forge PR: https://github.com/sp-prod-field/bnk-forge/pull/73

Both PRs must be merged together:

• This PR updates the catalog module definitions (variable names, TF resource addresses, outputs, defaults)
• The companion PR updates the bnk-forge templates and reconciliation targets to match

If this PR is merged alone, new deployments will create f5-cne-core/f5-bnk namespaces but templates will still send the old variable names (filtered out by OpenTofu).
If the companion is merged alone, templates will send cne_core_namespace/cne_instance_namespace but the catalog module won't accept them (variables not declared).