The original implementation created/destroyed framebuffers (FBs) per-frame, leading to kernel overhead and screen tearing. This commit replaces it with a different approach using:
- Asynchronous `drmModePageFlip()` with vblank sync
- Framebuffer caching to reduce repeated FB creation/removal operations
- Proper resource management through BO callbacks and buffer release synchronization
- Added error handling for busy displays, cache overflows, and flip failures
- Event-driven cleanup via page_flip_handler to prevent GPU/scanout conflicts

Co-authored-by: rob-bits

[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.

Update RGFW to 1.7.5-dev

RGFW: fix Escape always closing the window

Update RGFW to 1.7

[rshapes] Add DrawEllipseV and DrawEllipseLinesV

Update comments

Update comment (gamepad axes)

RGFW backend: add missing Right Control key

Remove unused variable

Found some issues with output size when padding required, just re-implemented both functions from scratch.

Note that returned output size considers the NULL terminator as an additional byte.