br/streamhelper: fix panic while removing task (#50869)

[ti-chi-bot]

This is an automated cherry-pick of #50869

What problem does this PR solve?

Issue Number: close #50839

Problem Summary:

What changed and how does it work?

This PR will do the nil check over the checkpoints.
This PR also will catch the panic generated during the subscription handler.
And some locking are acquired during handling incoming tasks.

Check List

Tests

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

  • I checked and no code files have been changed.

Release note

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

Fixed a bug that may make TiDB panic when stopping a log backup task.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (release-7.5@d686efd). Click here to learn what that means.
The diff coverage is 79.4117%.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #51053   +/-   ##
================================================
  Coverage               ?   71.9876%           
================================================
  Files                  ?       1403           
  Lines                  ?     407363           
  Branches               ?          0           
================================================
  Hits                   ?     293251           
  Misses                 ?      94385           
  Partials               ?      19727           

Flag	Coverage Δ
unit	71.9876% <79.4117%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9913% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	53.2990% <0.0000%> (?)

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger, YuJuncen

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:

• br/OWNERS [BornChanger,YuJuncen]

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-02-07 09:56:32.436356402 +0000 UTC m=+350718.003126279: ☑️ agreed by YuJuncen.
• 2024-02-18 02:56:27.576142521 +0000 UTC m=+153076.323765631: ☑️ agreed by BornChanger.

[hawkingrei]

/retest

[3pointer]

if it catch the panic here. but this goroutine has no longer exists anymore.
do we need generate this for loop again?

[YuJuncen]

If a random panic happens, the caller may or may not require retry this loop. I think it will be better to don't regenerate this loop and make the caller to decide whether to spawn another loop.

Perhaps we can add some mark about whether the goroutine is still running later. Anyhow that is out of this PR's scope, which focus on restricting the panic in the scope of log backup advancer.

[3pointer]

rest LGTM

[YuJuncen]

/retest-required

[BornChanger]

/retest