[breaking, wrapper] Improve distinct handle and location type decls

[hazeycode]

Includes fix to UniformLocation underlying type. -1 (invalid location) can be passed to some uniform procs per the spec.

[Copilot]

Pull Request Overview

This PR improves the handle and location type declarations for the wrapper by replacing plain extern structs with enums that include explicit invalid values, in accordance with spec allowances (e.g. UniformLocation accepts –1 as valid for special cases).

• Replaces several extern struct declarations with enums for stronger type safety.
• Updates many API calls by converting enum values consistently via @intFromEnum and adding appropriate assertions.
• Improves error detection by asserting against invalid enum states before calling underlying binding functions.

Comments suppressed due to low confidence (3)

src/wrapper.zig:3312

• The original code passed 'buffer.name' and now uses @intFromEnum(buffer), implying that the enum encapsulates the underlying value. Please confirm that this conversion correctly represents the intended value and update documentation if needed.

            bindings.bindBufferRange(@intFromEnum(target), index, @intFromEnum(buffer), offset, size);

src/wrapper.zig:2735

• The assert ensuring 'name.len > 0' implies empty names are not allowed. Please verify that this behavior aligns with the expected API usage and document the rationale if empty names might occur.

            assert(name.len > 0);

src/wrapper.zig:2556

• Switching from bitCast-based conversions to using @intFromEnum is a good move, but please double-check that the semantics—especially for handles with possible negative values like UniformLocation—are preserved throughout all similar functions.

            assert(program != Program.invalid);