fix potential nil panic in apexlogs handler
fix potential nil panic in apexlogs handler

I was missing h.once.Do() in Flush() etc, so the buffer could be nil,
but really once is unnecessary here anyway

apex/log