Failsafe command

## Describe your suggestion
Sometimes due to bugs/lag in a server the player might get stuck in dangerous situations that the autopilot can't get out of. My suggestion would be a setting called "failsafeCommand" that would be run if something isn't going the way it should (see Settings for explaination). This is particularly useful in servers that have plugins that let the player teleport to a safe location (home, waypoints, warps).

## Settings
Baritone could detect if it is in a risky situation either if it's been stuck for too long in the same position (a specifiable radius perhaps), if the player is being repeatedly harmed (mob avoidance failure) or if it's on fire (fell in lava). Moreover, an autodisconnect feature could also be implemented separatedly that acts the same way but instead of a command it automatically disconnect the player from the server for safety.

## Context
The suggestion would bring an immense improvement to the autonomy of the system, so much so that users could for example leave baritone mining or travelling without having to constantly supervise if anything goes wrong, in the event of which most times right now it cannot gain control back quickly enough to avoid death. What brought me to write this suggestion is this now having happened many times to me during automine sessions.

## Final checklist
- [ ] I have not used any OwO's or UwU's in this issue.

Start by locating the Settings implementation and the existing autopilot, automine, and mob-avoidance handling described in the issue. Define the safety conditions, configurable failsafe command, and optional autodisconnect behavior before assessing implementation scope; done should include tests for each trigger and the resulting action.

Written by the indexing model from the issue text.