I'm not sure what that groups state actually does or whether it matters, but you could try changing the device type to "device," saving it, click the "clear all states" button, change the device type back to what it is now, and clicking "save" again. If there's a configure button I'd click that too. However if that data is somehow stored in the bulb it may come right back.
Didn't work. I tried switching it to a few other device types - Generic Zigbee Bulb, Generic Zigbee Dimmer, Group Dimmer - and clicking all the buttons possible, nothing worked.
It's possible the group IDs get read from the device and stored in state, so if it got assigned one for some reason, that could be the cause, and a reset/re-pair of the device should get rid of it (but that probably shouldn't have happened unless you had a group defined in Hubitat, removed it, and the device didn't get that message for some reason, maybe because it was offline at that time). No need to remove the deicxe first, though you may need to use the "Device" driver again to clear it if you want. If you linked a non-Hubitat remote/button device to the bulb, that might also have done it, though I don't recall how most of those work.
But it's also probably harmless to leave. It will respond to Zigbee group mesaages addressed to that group, but if you don't have such a group on Hubitat on the first place, that shouldn't happen.
You're probably right- this device must have been a part of Group 4600 and never received the command to leave it. Weird though because (as the name implies) it has a sister device "Drive Light North" and it did not have this problem. And I highly doubt I included the South device in a group and not the North device.
Oh well, all's good now. If this happens again, hopefully I'll have some logs or more info to support it.