D8H

I did a pass on todo. * In the behaviors, only one remain on the debug drawing. * In the NavMesh generator, it's remainders of the part of CritterAI implementation...

I published the NavMesh generator as a library. I made a few changes to avoid some reallocations when updating meshes. I think I'll integrate it the same way as the...

For the library, I left a catted TS instead of a packaged library because I think it will be easier to debug, but I could package one if your want.

It gets a bit messy when the NavMesh is shown with hitboxes.  I guess we could - Add a new action to hide or show the debug layer -...

I also changed the descriptions to start with a verb. It is a recommendation to write documentations in the wiki and I thing it apply well for behavior descriptions. It...

I added 2 parameters to allow a clear debug view for the behavior to draw on it. 

> @D8H Reading through this PR and the original discussion, I noticed there isn't an action to stop movement on the path. Is that something you would consider adding? >...

> When should this behavior be expected approximately? Probably not soon. We should probably rather add a shared properties feature to events-based behaviors and make this a community extension.

It's scene properties where the rastering grid is setup for this extension. Events-based bavariors can only define properties to be set on objects for now.

Tested on: - Preview - Liluo.io - Windows - Android