Pass `updated_at` to get only incremental changes since last update

Feedback:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7617#note_18762721

They were Rails' default and are unnecessarily overridden.
Signed-off-by: NDavid Wagner <david@marvid.fr>

Conflicts:
	app/models/ci/pipeline.rb
	app/models/commit_status.rb

which merges previous exclude_ignored_jobs and failed_but_allowed,
so that we don't treat ignored a special case in HasStatus.

This solves Pipelines in `running` after all stages do finish.

This reverts commit 575dc2b0.

Because pipeline status could be changed for the builds in the next
stages, if we process next stages first, the current build would be
out of synchronized, and would need a reload for that matter.

Alternatively, like what I did in this commit, we could process the
next stages later (by using `after_transition` rather than
`around_transition`), and complete what're doing for the current
build first. This way we don't have to reload because nothing is
out synchronized.

Note that since giving `false` in `after_transition` would halt the
callbacks chain, according to:

https://github.com/state-machines/state_machines-activemodel/blob/v0.4.0/lib/state_machines/integrations/active_model.rb#L426-L429

We'll need to make sure we're not returning false because we don't
intend to interrupt the chain.

This fixes #22010.

After this fix, both pipeline events and build events would only show
up once.