Sync version macros with v1.1.0 release

Effort: Small — Impact: Medium — Priority: 8 of 8

The declared version is behind the newest published tag. Git tag v1.1.0 (released 2026-05-01) is an ancestor of master (at commit 82056c3), but all three version locations still say 1.0.2:

• NK_GAMEPAD_VERSION / _MAJOR / _MINOR / _PATCH at nuklear_gamepad.h:30-33
• project(... VERSION 1.0.2) at CMakeLists.txt:5
• The version assertions in test/nuklear_gamepad_test.c:31-34

About ten PRs have merged since v1.1.0 (L2/R2/L3/R3 buttons #59, axis names #55, version macros #56 themselves, axis clamping #71, backend fixes #69/#70), so master is well past 1.1.0 in content too.

Suggested Implementation

Bump all three locations to the next intended release (1.2.0, given the feature additions since v1.1.0) in one commit, and note in the PR that future releases should update these alongside the tag — the three spots must move together (the test asserts the header, and CMake duplicates it).

QA

• grep -rn "1\.0\.2" in the repo (excluding vendor/) returns nothing.
• Header macros, CMake project version, and test assertions all agree.
• ctest passes.

Start with the version definitions in nuklear_gamepad.h:30-33, the project version in CMakeLists.txt:5, and the assertions in test/nuklear_gamepad_test.c:31-34. Check the existing 1.0.2 references, update all three locations to the intended 1.2.0 release, then run the repository grep and ctest. Done means the locations agree, no non-vendor 1.0.2 references remain, and tests pass.