Handle all new CW/CCW tracks, tidy up the menu and use the official NPY files

[dmh23]

The new CW/CCW tracks highlight the need to refactor the track code.
It really should be driven off config rather than numerous classes.
The edge waypoints can come from the NPY files, as well as being the better place to get the official centre waypoints.
The menu should be ordered properly, and structured with sub-menus for the different variants of the same track
Also capture a few more track details / attributes in fields, like the CW/CCW direction indicator and so on....

[ykzeng]

agreed @dmh23 we struggled a bit while trying to load data for the latest monthly league race for clockwise rogue raceway track. Perhaps a refactoring is needed to load directly from any official npy track files?

[ykzeng]

also, we would appreciate if there's any quick guidance on the process due to adding a new track in the current class setting. specifically, how length/width/dividers/annotations can be generated/retrieved, ideally in an automated fashion based on the npy file.