The errors have some clues! Timed out trying to connect to CG Session, which suggests it’s trying to get a Core Graphics context, and Cancelled integration because headless test environment is required but not available after 60s, “headless” meaning no display attached, which is common for build machines. You might try connecting a display to the machine, log into it and see if the error goes away.
Some frameworks/libraries still expect a graphics context which may be dependent on a display (even if it’s virtual, like VNC). If the machine doesn’t start up with a monitor attached, the window server may not be able to init certain features correctly and you get weird results like this.
I’ve solved this type of problem in the past but connecting a headless display adaptor to each machine, which fools the graphics card into thinking there’s a display attached. You can find these dummy display emulators online for under $20.
Hope that’s helpful.