ci: always print engine logs on job failure

[jedevc]

Previously, these logging messages were only added on the publish job provisioning tests:

dagger/.github/workflows/publish.yml

Lines 251 to 256 in 9a0f81a

	- name: "ALWAYS print engine logs - especially useful on failure"
	if: always()
	run: docker logs $(docker ps -q --filter name=dagger-engine)
	- name: "ALWAYS print kernel logs - especially useful on failure"
	if: always()
	run: sudo dmesg

This meant that failures in the engine and cli jobs didn't trigger this type of message, and so makes crashes more difficult to debug. We already print the kernel logs, we just don't grab the engine logs.

This would have been useful when encountering #6234 when building off of master. Some clients returned the useful buildkit panic, however, at the same time, other clients simply got a 502 error - I suspect this was the same crash that brought down the whole engine, but it's difficult to confirm this currently without the engine logs.

[jedevc]

Right, I've just understood why we can't do this 😄

Because we just forward the socket for the dagger engine into each pod, we can't actually get the logs that are being created for the engine.