Update to newer Raylib versions

[eutro]

Bindings are semi-auto-generated, so it shouldn't be overly difficult. The things I was hung up on:

• [ ] Codegen for raymath
• [ ] Reviewing changes for raylib-2d

[eutro]

Notably, it may be worth parsing raylib.h itself with one (Racket-implemented) parser, and using it for raymath.h as well, to avoid having to 1. rely on raylib's parser; 2. duplicate code. Raylib's parser can still be used as a reference for what conventions Raylib headers generally follow. The header is already parsed as text for function typedefs (that weren't included in Raylib's parser output).