Backport to v0.114.x , IndexerService::apply_init_tip should stop after received exit signal.

[eval-exec]

Backport #4345 #4348

What problem does this PR solve?

Issue Number: close #4311

Problem Summary:

In the apply_init_tip function, there is a loop that should take into account the exit signal:

ckb/util/indexer/src/service.rs

Lines 156 to 172 in 1ee9c98

	loop {
	if let Err(e) = self.secondary_db.try_catch_up_with_primary() {
	error!("secondary_db try_catch_up_with_primary error {}", e);
	}
	if let Some(header) = self.secondary_db.get_block_header(&init_tip_hash.pack()) {
	let init_tip_number = header.number();
	let mut batch = self.store.batch().expect("create batch should be OK");
	batch
	.put_kv(
	Key::Header(init_tip_number, &init_tip_hash.pack(), true),
	vec![],
	)
	.expect("insert init tip header should be OK");
	batch.commit().expect("commit batch should be OK");
	break;
	}
	sleep(Duration::from_secs(1));

Additionally, once initial_syncing is finished and CKB receives an exit signal, there is no need to spawn the new_block_watcher polling job.

What's Changed:

Related changes

• handle exit signal in apply_init_tip

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code ci-runs-only: [ quick_checks,linters ]

Side effects

• None

Release note

Title Only: Include only the PR title in the release note.

[doitian]

Please rebase