fix: Don't allow publishing wildcards in MQTT topic

[Koenkk]

To prevent another: #26939

[Nerivec]

If a publish is done while starting (like that issue), it will still fail to start though since it throws, won't it?

[Koenkk]

In that case e.g. the HA discovery would fail (with a proper error).

[Nerivec]

If one of the extensions throws during start, it will fail to load the extension for example:

zigbee2mqtt/lib/controller.ts

Lines 267 to 271 in a2debc0

	try {
	await extension.start();
	} catch (error) {
	logger.error(`Failed to start '${extension.constructor.name}' (${(error as Error).stack})`);
	}

Nothing was throwing in that function previously (and no call to publish is try/catch-ed):

zigbee2mqtt/lib/mqtt.ts

Lines 215 to 222 in a2debc0

	try {
	await this.client.publishAsync(topic, payload, actualOptions);
	} catch (error) {
	if (!skipLog) {
	logger.error(`MQTT server error: ${(error as Error).message}`);
	logger.error(`Could not send message: topic: '${topic}', payload: '${payload}`);
	}
	}

[Koenkk]

Maybe its better to skip the publish and log an error?

[Nerivec]

Probably safer, would have to check every publish calls otherwise, and where they lead 😅