Deploy trigger logs are nested sentences

[edvgui]

The logs of a resource showing the reason of the deploy currently look like this:

Start run for resource ... because Deploy was triggered because a new version has been released
Start run for resource ... because Deploy was triggered because user has requested a deploy
Start run for resource ... because Individual deploy triggered for resource ... because last deploy happened more than 600s ago.

It looks like there is a second log starting in the middle of the log (after the first because). This is a bit silly, it could for example be changed to:

Deploy was triggered because a new version has been released: %(version)s
Deploy was triggered because user has requested a deploy
Individual deploy triggered because last deploy happened more than 600s ago.

I think the second half of the log is plenty enough, and it doesn't need to also include the resource id, we already know which resource this is about (log prefix in files or resource page in the web-console)

[wouterdb]

If you read the resource action log, you don't know which resource the log line belongs to if we remove this...

[edvgui]

If you read the resource action log, you don't know which resource the log line belongs to if we remove this...

Oh, I thought the log would have the same prefix as all other resource action logs. But if that is not the case then indeed something about the resource needs to stay