Add a command to remotely trigger command blocks without redstone

Suggestion:
Add a new command to remotely trigger a command block with a virtual redstone pulse. For example, /activate <x> <y> <z> or /trigger_block <x> <y> <z>. This command sends a logic‑level signal to the specified command block, causing it to execute once exactly as if powered by redstone, but without placing any physical block (redstone dust, redstone block, etc.). It works remotely, even across dimensions.

Why needed:
Currently, command blocks only have two activation methods: redstone signal (requires physical blocks and space) or always‑active (continuous execution, unsuitable for single triggers). Many compact builds, such as high‑speed ships and complex vehicles, need precise single‑trigger activation in extremely limited space where redstone wiring is impossible. This feature provides a zero‑footprint, purely logical trigger, saving space and reducing lag.

Not a replacement:
Redstone remains best for physical interactive builds; always‑active for continuous systems. This suggestion fills the missing gap of logic‑level single‑trigger with no block footprint.