owner: fix data race on ownerManager.campaignCancel (#56362)

[ti-chi-bot]

This is an automated cherry-pick of #56362

What problem does this PR solve?

Issue Number: close #56053

Problem Summary: m.campaignCancel is currently set in campaignLoop goroutine, which might happen after calling campaignCancel() that access m.campaignCancel, even though it is called after CampaignOwner().

What changed and how does it work?

Set m.campaignCancel in CampaignOwner() rather than in campaignLoop goroutine, to ensure a campaignCancel() called after CampaignOwner() can always access m.campaignCancel instead of nil.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release-7.1@0627e65). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.1     #57019   +/-   ##
================================================
  Coverage               ?   73.4857%           
================================================
  Files                  ?       1212           
  Lines                  ?     381319           
  Branches               ?          0           
================================================
  Hits                   ?     280215           
  Misses                 ?      83213           
  Partials               ?      17891           

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lance6716, tangenta

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [lance6716,tangenta]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-11-11 08:22:15.350158149 +0000 UTC m=+258097.541027139: ☑️ agreed by lance6716.
• 2024-11-11 09:12:12.789411358 +0000 UTC m=+261094.980280355: ☑️ agreed by tangenta.