Prevent collision between KUnifiedPush DBus and KRunner DBus

These share the same D-Bus service name (org.kde.neochat) which comes
with a fun little addition: KRunner activation! While this is not a
problem while NeoChat is running - since it's already registered - this
becomes an issue while searching for NeoChat in something like the
Kickoff. The Kickoff (and consequently, KRunner) tries to activate the
NeoChat D-Bus service which runs our unified push parts.

This introduces a "FakeRunner" which watches closely for calls to the
KRunner interface while we're in unified push mode (or directly called
from D-Bus but not running) so it quits immediately.

src/fakerunner.h

@@ -0,0 +1,31 @@
+// SPDX-FileCopyrightText: 2024 Joshua Goins <josh@redstrate.com>
+// SPDX-License-Identifier: GPL-2.0-only OR GPL-3.0-only OR LicenseRef-KDE-Accepted-GPL
+
+#pragma once
+
+#include <QDBusContext>
+
+#include "runner.h"
+
+/**
+ * This is a close-to-identical copy of the regular Runner interface,
+ * only used when activated for push notifications. This stubs it out so
+ * Plasma Search and Kickoff doesn't accidentally activate the push notification
+ * service.
+ *
+ * @sa Runner
+ */
+class FakeRunner : public QObject, protected QDBusContext
+{
+    Q_OBJECT
+    Q_CLASSINFO("D-Bus Interface", "org.kde.krunner1")
+
+public:
+    Q_SCRIPTABLE RemoteActions Actions();
+
+    Q_SCRIPTABLE RemoteMatches Match(const QString &searchTerm);
+
+    Q_SCRIPTABLE void Run(const QString &id, const QString &actionId);
+
+    FakeRunner();
+};