Things for estimate_best_time

[StructuralMike]

Some things to consider in the processing:

This should increase the amount of matching segments to match times for:

• After events such as S/Q, entering a dungeon, and similar, the pathing PRIOR to that doesn't matter in a particular segment. Should be easy to just set those to a dummy variable like 20_002
• Similar reasoning applies after those events in a particular segment.

Segment database:

• The full segment database should be pre-generated and saved as a datafile for loading so that it doesnt need to be generated each time a new run is tested. Not important right now, but when the run catalogue gets big, generation time increases a lot.
• This also allows anyone access to comparative data using the repo

Logic application:

• Should be dynamically applied to the current room. I.e. if it is a kill-room, check weapons, otherwise just use standard movement logic.