Feature/baritone flow

[Imajio]

Type of change

• Bug fix
• New feature

Description

Adds a Baritone category to Meteor's module list with a friendlier way to drive
Baritone, plus a visual, n8n-style node-flow editor for chaining tasks together.

New Baritone category (own icon) with one-shot command modules, each bindable to
its own keybind like any other Meteor module - press the key, the action fires once,
the module resets itself ready for the next press:

• Goto - path to a fixed coordinate
• Mine - mine a configured block list
• Follow - follow the nearest player, nearest entity, or a named player
• Pause / Resume / Stop - control the current path
• Command - run a raw Baritone command

Flow Builder module - build, save and run visual flows that chain multiple steps
together (Baritone tasks, Meteor module actions, and client actions) via a draggable
node canvas:

• Drag nodes, wire them by dragging from a node's output port onto another node
• Module nodes: enable/disable/toggle any Meteor module, or set one of its settings
  by name/value, directly from a flow
• Trigger nodes: On Player Near Appear fires when a new player enters a
  configurable radius (edge-triggered, not just "someone is near")
• Client-action nodes: Leave (disconnect) and Reconnect (rejoin the last server)
• Flows can be armed so their trigger nodes are watched in the background and start
  the flow on their own - e.g. On Player Near Appear -> Leave -> Wait (30 min) -> Reconnect. The module stays subscribed across disconnect/reconnect
  (runInMainMenu) so an armed flow keeps progressing while logged out.

Reasoning: Baritone is powerful but has a steep command-line learning curve.
Exposing its common actions as ordinary bindable modules, and letting more complex
automation be built visually instead of via chained chat commands, makes it far more
approachable - especially for anarchy-server workflows (auto-leave/reconnect on player
detection, farming loops, etc.) that previously required external scripting.

The one-shot Baritone modules replace the "Quick Task" buttons that were originally
embedded in the flow module itself - once they existed as standalone bindable modules,
keeping duplicate buttons inside the flow module's widget would have been redundant, so
that group was removed.

Related issues

N/A

How Has This Been Tested?

• used to run away from the 2b2t spawn :)

Checklist:

• My code follows the style guidelines of this project.
• I have added comments to my code in more complex areas.
• I have tested the code in both development and production environments.