This was libc attempting to detect insufficient stack space, under the assumption of a guard page. Go chose to not create a guard page. Nobody can force you to fasten your seatbelt.
But nobody requires that you fasten your seatbelt, either. I believe a stack check is still opt-in using the default flags on most compilers, unless you alloca. Plus, stack probes are merely precautionary, they can still be broken by an inconvenient sequence of stack allocations and signal handlers being run.
Not libc. The stack probe was inserted by the compiler when compiling the vDSO (part of the kernel, but mapped into user processes) with certain ricer^Whardening flags enabled.