Quake like camera animations and strafe jump movement

Calculate `right` Vector3 for correct audio stereo positioning.

...instead of relying in src/raylib provided one. #4900

The creation of the array has been rewritten, the size of the example has been reduced

A review of the code is required.  Since I'm not sure what's written correctly at all.

This example enables HIGHDPI and renders a scale showing how the logical
size compares to the pixel size of the window.

The core_window_flags example automatically restores the window from
being minimized after 3 seconds. However, it only resets the frameCounter
if the window is minimized through the app from inputting KEY_N.  This
means if you miminize the window by other means (like pressing the minimize
button) then the example will immediately restore the window because the
frame counter wasn't reset. I've fixed this by setting the frameCounter
back to 0 once it's expired. I also added a note in the UI that the example
automatically restores the window so it's not a surprise.

I think this line was accidently commented out in this commit:

3d1ae3500c

The FPS limit is needed to get the desired wait time for the "hide window"
test, which uses the frame counter to hide the window for 3 seconds. On
my machine without this limit it runs at over 1000 FPS and it appears
like the hide window state is broken.

I also added some text that tells the user that it only hides the window
for 3 seconds so they're not surprised when the window automatically
reappears.

Removes the second build.zig in the examples directory and incorporates it
into the main build.zig. This gives the zig build system the data needed to
know if the raylib library needs to be rebuilt when running any example.

This compensate for slower zoom speed due to log scaling

Fixes warning: narrowing conversion caused by trying to convert int to unsigned char

* Reorganize some conditions to fix overlap bugs

* Fix edge case where control point selection outlives mouse down

...so it will always prioritize local version of raylib instead of
system-wide installations, which is a huge problem when testing any
changes done locally to raylib as it might cause silent mismatch issues.
There were only 4 examples affected by this issue which were using
`#include <raylib.h>`. Other examples use proper `#include "raylib.h"`

Fixes: https://github.com/raysan5/raylib/issues/4820