log_backup: fix panic during advancer owner transfer (#52671)

[ti-chi-bot]

This is an automated cherry-pick of #52671

What problem does this PR solve?

Issue Number: close #52597

Problem Summary:

1. When losing the advancer ownership, the channel for subscription may be full.
2. the consumer has already gone due to the canceled context. Hence making the producer(subscription) goroutine stuck.
3. After the graceful shutdown period, the output channel will be eventually closed and we will get a send on closed channel panic.

What changed and how does it work?

• When sending to the channel, also select the context.
• Catch all panic and convert them to errors (so we can retry.)

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.

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.

Fixed a bug where TiDB may panic when log backup enabled and PD is unreachable.

[YuJuncen]

/retest-required

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [Leavrth]

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-04-18 07:43:15.060311289 +0000 UTC m=+496814.171357741: ☑️ agreed by BornChanger.
• 2024-04-18 08:01:09.884897143 +0000 UTC m=+497888.995943593: ☑️ agreed by Leavrth.