Add ops connections and recommendation blocks for newer databases

[ArnobKumarSaha]

ResourceDescriptors — hub/resourcedescriptors/ops.kubedb.com/v1alpha1/

Added spec.connections (the same MatchRef on {.spec.databaseRef.name} with the ops label that mysqlopsrequests.yaml already had) to the 14 ops RDs that were missing it:

aerospike, cassandra, clickhouse, db2, documentdb, etcd, hanadb, hazelcast, ignite, milvus, neo4j, oracle, qdrant, weaviate

Target apiVersion is kubedb.com/v1alpha2 for all 14 — those kinds exist only under v1alpha2 (unlike MySQL, which points at kubedb.com/v1). Kinds taken from the corresponding hub/resourcedescriptors/kubedb.com/v1alpha2/*.yaml labels (DB2, DocumentDB, HanaDB, ClickHouse, Neo4j, Etcd, …).

ResourceOutlines — hub/resourceoutlines/kubedb.com/v1alpha2/kubedb/

Added the supervisor Recommendations block to the Operations page (right after Recent Operations, matching v1/kubedb/mongodbs.yaml) of the 11 outlines that were missing it:

cassandras, ignites, milvuses, neo4js, oracles, qdrants, rabbitmqs, singlestores, solrs, weaviates, zookeepers

The block is byte-identical to the existing copies in clickhouses.yaml / druids.yaml.

Deliberately not included

• v1alpha2/kubedb/kafkas.yaml has no Operations page at all, so there is nowhere to append the block — adding one would mean creating the whole page. v1/kubedb/kafkas.yaml already has both blocks.
• db2s.yaml, documentdbs.yaml, hanadbs.yaml outlines were left alone — those DBs are not in the supervisor recommender set.

Verification

cmd/resource-fmt produces no further diff, cmd/check-edge-label and cmd/check-embed exit 0, go build ./... is clean. make fmt could not run locally (Docker daemon down), but the native resource-fmt / check-edge-label passes cover the two hub-specific passes it wraps.