Beyond The End - Optimization and Fixes

    Add flybench worldgen benchmark and skip hardware info in discarded reports

    /bteopt flybench <dimension> [blocks/s] [distance] simulates a player
    flying: it puts the player in spectator and moves them in a straight
    line towards +X at a constant speed per tick (Y = 200 in the Overworld,
    100 elsewhere). It records server tick times (mean, p50/p95/p99, max,
    ticks over 50 ms), unloaded chunks within view distance (total and
    ahead), ticks with the player in an unloaded chunk and real versus
    ideal travel time, and runs the worldgen profiler for the whole flight,
    tagging every sample with the 250-block route segment ("[tramo x=..]")
    so slow zones can be analysed on their own. It writes
    logs/bteopt_flybench_<dimension>_<date>.txt and restores the player's
    game mode. /bteopt flybench stop ends it early. Debug tool only.

    StructureTemplate#createEntityIgnoreException ignores entities that fail
    to load, but Entity#load first builds a full CrashReport whose
    SystemReport queries the GPU, CPU and memory through OSHI, only to be
    thrown away (~1 s of the worldgen serial queue in the Nether flybench).
    While that method runs, skip the hardware part of SystemReport. Whether
    the entity is created does not change and any other crash report is
    still complete.