* Use explicit atomics

* missed one

* use relaced ordering

* core_loading_thread example join thread on completion

* error checking

canJump used to alternate between true and false when on ground

This reverts commit 4f6fbaed41.

Those functions were platform dependent and user has no control over the file created. They have been removed from raylib and just moved to `core_storage_values` example.

This example requires a complete remake to be more clear. Also current quaternion maths could have issues.

REDESIGNED: `LoadDirectoryFiles()`
ADDED: `LoadDirectoryFilesEx()`
REDESIGNED: `LoadDroppedFiles()`
ADDED: `IsPathFile()`

This BIG BREAKING change simplifies the functions and gives more control to the user:
 - A new `struct FilePathList` has been added to avoid exposing complex pointers.
 - User is responsible of memory loading/unloading
 - Filepaths loading support recursive directories and file extension filters

RENAMED: `ClearDroppedFiles()` to `UnloadDroppedFiles()`

As prior commit, but complete fix for XBox controller and trigger
buttons too.

> The joystick range is a float from -1 through +1. Casting this to int
> yields only three possible values: -1, 0, and 1. This gives a
> misleading joystick placement in the demo.
>
> By casting to int after the multiplication to get pixel values, the
> demo reveals the analog feel of the joystick.

The joystick range is a float from -1 through +1. Casting this to int
yields only three possible values: -1, 0, and 1. This gives a
misleading joystick placement in the demo.

By casting to int after the multiplication, the demo reveals the
analog feel of the joystick.

CONVENTIONS:
  - Functions are always self-contained, no function use another raymath function inside, required code is directly re-implemented inside
  - Functions input parameters are always received by value
  - Functions use always a "result" variable for return
  - Functions are always defined inline
  - Angles are always in radians (DEG2RAD/RAD2DEG macros provided for convenience)

Some functions/values have been deprecated for long time but some mapping was kept for convenience. Some of those mappings have been removed...

Moved outside BeginDrawing()/EndDrawing() to illustrate drawing is happening to an external texture (not screen)

Co-authored-by: Jeffery Myers <JefMyers@blizzard.com>