cluster: recovery for cloud topics metastore and topics

This implements the body of the cluster restore stages for cloud
topics, by restoring the metastore, and then calling create topics on
all the desired cloud topics.

One of the invariants that we're trying to uphold is that the metastore
topic will have the same remote_label after restoring as the original,
in order (this has the nice property of being able to point at the
metastore from a topic manifest, e.g. for read replicas).

To that end, restoring the metastore looks like:
1. creating the metastore topic
2. calling restore
3. upon success, updating the metastore topic's remote_label to be what
   it was in the dead cluster

After this happens, we go ahead and create all the cloud topics, which
is only partially implemented in this commit: we create the topics, but
additional logic is needed to get the restored topics to bootstrap their
ctp_stms from the metastore. That is left as separate work.

Author: andrwng

src/v/cloud_topics/tests/BUILD

@@ -92,3 +92,27 @@ redpanda_cc_gtest(
         "@googletest//:gtest",
     ],
 )
+
+redpanda_cc_gtest(
+    name = "cluster_recovery_test",
+    timeout = "moderate",
+    srcs = [
+        "cluster_recovery_test.cc",
+    ],
+    cpu = 1,
+    deps = [
+        ":cluster_fixture",
+        "//src/v/cloud_storage",
+        "//src/v/cluster",
+        "//src/v/cluster/cloud_metadata/tests:cluster_metadata_utils",
+        "//src/v/kafka/server/tests:kafka_test_utils",
+        "//src/v/random:generators",
+        "//src/v/ssx:future_util",
+        "//src/v/ssx:sformat",
+        "//src/v/test_utils:gtest",
+        "//src/v/test_utils:scoped_config",
+        "//src/v/utils:retry_chain_node",
+        "@googletest//:gtest",
+        "@seastar",
+    ],
+)