AstraMarket

[REFACTOR] Create MultiplatformCommand in CoreModule

The command error handler lives in CoreModule and needs it to find the sender, so the command module now takes it from there instead of receiving its own copy.\n[FEAT] Tell the sender why a command failed

The old handler answered only a missing permission and logged everything else, so a console running a player command or a mistyped price got no reply. One handler in CoreModule now answers every failure with a text from error.\n[FEAT] Tell the sender the exact reason a command failed

An unknown player or a bad argument value read as "wrong usage". Each AstraLibs exception now has its own text. A sender the platform cannot wrap, such as a command block, made the handler itself throw; now the failure is only logged.\n[FIX] Let unexpected command failures reach the server log

withoutParentHandlers() leaves the logger with no handler at all, so the old BrigadierErrorHandler, and its successor, dropped every stack trace they logged.\n[CHORE] Bump version to 1.34.0\n[DOCS] Remove the KDoc this change added\nMerge pull request #147 from Astra-Interactive/feat/command-exception-handler

[FEAT] Tell the sender why a command failed