fix: add events when pre- or post-upgrade check fails (backport #3211)

[mergify]

Which issue(s) this PR fixes:

longhorn/longhorn#9643, backport issue for longhorn/longhorn#9569

What this PR does / why we need it:

Add an event when upgrade pre- or post-check job completes, either with error or success message.

Special notes for your reviewer:

Additional documentation or context

Summary by CodeRabbit

• New Features

  • Enhanced event broadcasting and recording capabilities during the upgrade process.
  • Improved logging for pre-upgrade checks and outcomes.

• Bug Fixes

  • Simplified event handling by streamlining the event broadcaster functionality.

• Documentation

  • Updated comments for better clarity on upgrade path checks.

---

This is an automatic backport of pull request #3211 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of e6ce3f2 has failed:

On branch mergify/bp/v1.7.x/pr-3211
Your branch is up to date with 'origin/v1.7.x'.

You are currently cherry-picking commit e6ce3f26.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   app/post_upgrade.go
	modified:   app/pre_upgrade.go
	modified:   app/recurring_job.go
	new file:   app/util.go
	modified:   constant/events.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   upgrade/upgrade.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[derekbit]

Will merge it after v1.7.2 is out

[derekbit]

@james-munson Found some conflicts.

[james-munson]

Fixed conflicts and re-based. Ready to go.