Improve Actions status aggregations

[wxiaoguang]

Make the result the same as GitHub:

• all skipped, then result is skipped
• any cancelled, then result cancelled

[TheFox0x7]

Is Unknown a status which should change the final result? For example combination Skipped, Success, Unknown resolves currently to Skipped which isn't consistent with behavior of Skipped, Success combination.

[wxiaoguang]

Is Unknown a status which should change the final result? For example combination Skipped, Success, Unknown resolves currently to Skipped which isn't consistent with behavior of Skipped, Success combination.

Good catch, added more cases and comments in f438b56

[TheFox0x7]

LGTM
I'll check how Github treats all skipped workflows later.

[delvh]

I would say yes:
As I see it, a skipped job is mainly something like execute on hardware xy, but it wasn't available. Or perhaps something like only execute once a month. Still, that doesn't prevent the PR from merging.

[TheFox0x7]

Confirmed, skips are treated as a pass:
TheFox0x7/repro#1
And cancellations as fails:
TheFox0x7/repro#2

[wxiaoguang]

The "actions status to commit status" converting seems consistent:

gitea/services/actions/commit_status.go

Lines 143 to 154 in 22c4599

	func toCommitStatus(status actions_model.Status) api.CommitStatusState {
	switch status {
	case actions_model.StatusSuccess, actions_model.StatusSkipped:
	return api.CommitStatusSuccess
	case actions_model.StatusFailure, actions_model.StatusCancelled:
	return api.CommitStatusFailure
	case actions_model.StatusWaiting, actions_model.StatusBlocked, actions_model.StatusRunning:
	return api.CommitStatusPending
	default:
	return api.CommitStatusError
	}
	}

[wxiaoguang]

Updated the comment in #32861 (with more trivial fixes)

[wxiaoguang]

Let's merge this as-is since 1.23 is releasing soon. We can do more improvements in the future if we have new ideas and samples.