Prepare v0.7.0

[ohchase]

Check if the public API is stable, try to actually make a future proof plan for moving towards a 1.0.0 stable api.
Everything needs documentation, or at least much more thorough documentation.
All functions with unsafe blocks that are exposed publicly as safe need safety clauses.
Make sure there is no panic spots, and document accordingly as well.
Try to move away from TrinityCore usage, to make it clear this is also available for any general 3d mesh navigation where you are willing to use a non rust code base in favor of linking against the actively maintained c++ recast navigation project and for guaranteed feature parity if you are migrating a project.

[ohchase]

v0.7.0, v0.6.0 was implemented as stop gap to get some dependencies upgraded and remove send/sync impls