Just as I posted that I found a workaround, but I would still like to know how to correct this.
For those that are having the same issue and just "want it done" here's what I did: On a fresh bitbake run, when gn-native failed, it showed me the command-line that it ran, which looked something like this:
cd /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/build && /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/recipe-sysroot-native/usr/bin/python3-native/python3 /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/git/src/3rdparty/gn/build/gen.py --no-last-commit-position --out-path /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/build/ --cc /home/aaron/yocto/build-raspberrypi-armv8/tmp/hosttools/gcc --cxx /home/aaron/yocto/build-raspberrypi-armv8/tmp/hosttools/g++ --ld /home/aaron/yocto/build-raspberrypi-armv8/tmp/hosttools/g++ --platform linux --ar /home/aaron/yocto/sources/poky/scripts/native-intercept/ar --qt-version 6.8.0.qtwebengine.qt.io && /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/recipe-sysroot-native/usr/bin/ninja -C /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/build/ gnRight around where it says gen.py notice there's a bunch of flags: --no-commit-position --out-path etc. Somewhere in those flags, add --allow-warnings and re-run that command. gn-native will (hopefully) build successfully, with warnings, and you will be able to proceed with your Yocto build.