`DrawRectangleGradientEx` as they were inverted.

[Zig] Fix issue on zig build Emscripten run if no emsdk installed

[zig] Add run examples using zig and emscripten for web

docs: mention another Common Lisp binding

[rmodels] Fixing offset for processing tangents for GLTF/GLB loading

[example] Fix pbr example shaders to use vec4 for vertexTangent

[zig] Update emsdk version for zig build to fix the issue with the EM_BOOL

Fix typo on config.h

[rcore] Fix ScanDirectoryFilesRecursively

Fixes a regression since 5.5, where `ScanDirectoryFilesRecursively` no
longer does the "recursively" part due to `path` being `static`.

The issue was once already fixed in
5530a3ceb8
but recently made it back it in.

bindings: add Raylib-cs.BleedingEdge

Update RGFW

Allow passing options to raygui in build.zig

add uiua bindings to the list

[examples] : adding new fancy clock

Update miniaudio to v0.11.22

Change `RGFW_window_eventWait` timeout to -1 to fix `EnableEventWaiting`

[rshapes] Fix incorrect parameter names in DrawRectangleGradientEx

Add LICENSE to build.zig.zon

add const qualifier to ImageDrawTriangleFan and ImageDrawTriangleStrip arguments

Examining the code shows that the rectangle is drawn winding counterclockwise, starting
with the top left. Therefore the colors used should be in the order: topLeft, bottomLeft,
bottomRight, topRight.

However, the variables actually being used are topLeft, bottomLeft, topRight,
bottomRight. I was confused by this as I was getting striping where I didn't expect any.
Put another way, the last two parameters are misnamed.

This diff swaps the parameter names and their usages. The result is that no runtime
behaviour changes: the same parameter order yields the same visual result both before and
after this change, but the parameter names now correctly reflect what they are actually
used for.

You can actually see this in the implementation of DrawRectangleGradientV, which
(correctly) passes top, bottom, bottom, top to DrawRectangleGradientEx.