feat: implement type safety

[TomerAberbach]

• Implement type-level checking of graph constraints
• The above requires an API change, to separate the keys representing a task from the task function
• Delete debug runtime validation entrypoint since the type-level validation takes care of it
• Reduce bundle size
• Increase test coverage
• Deprecate grfnviz since it's a pain to maintain and no one seems to be using it
• Require node 18

[TomerAberbach]

@maraisr since you're one of the people I know uses this, do you have any feedback? Does this look good to you at a high-level?

[maraisr]

This is such an wonderful pull request! 🎉 Thank you so much!!

Was messing around with it, and stumbled upon this nugget. Being able to detect a single output vertex is such a major win for stability and assurance.

I'd say ship it! 🚀

My only critique (though pales in comparison to the wins) is that I was unable to get autocomplete for dependencies, but its no biggy.

Example

let get = grfn({
	get_post,
	get_comments: [get_comments, ['get_post']],
	get_author: [get_author, ['get_post']],
	format: [
		(comments: string, post: string, author: string) => {
			return {
				comments,
				post,
				author
			};
		},
		['get_comments', 'get_post', 'get_au ▌']
//                                                   ^ expected intellisense to provide me with "get_author"
	]
});

let result = await get('my-post');
console.log(`result: %o`, result);

[TomerAberbach]

This is such an wonderful pull request! 🎉 Thank you so much!!

Was messing around with it, and stumbled upon this nugget. Being able to detect a single output vertex is such a major win for stability and assurance.

I'd say ship it! 🚀

My only critique (though pales in comparison to the wins) is that I was unable to get autocomplete for dependencies, but its no biggy.

Example

Glad it's working well for you! Agreed that autocomplete for dependencies would be nice. Might very well be possible to support...