Value-like macro using `UINT64_MAX` generates `nuint` type incorrectly on Unix

[Happypig375]

#757 seems to not have fixed the following case:

#include <stdint.h>
#define B3_DEFAULT_CATEGORY_BITS UINT64_MAX
#define B3_DEFAULT_MASK_BITS UINT64_MAX

with -g macro-bindings, this generates

    [NativeTypeName("#define B3_DEFAULT_CATEGORY_BITS UINT64_MAX")]
    public const ulong B3_DEFAULT_CATEGORY_BITS = 0xffffffffffffffffUL;

    [NativeTypeName("#define B3_DEFAULT_MASK_BITS UINT64_MAX")]
    public const ulong B3_DEFAULT_MASK_BITS = 0xffffffffffffffffUL;

on Windows but nuint type on Unix.

[tannergooding]

This is likely “correct” and comes from long or similar being the underlying type used by the macro