feat: adaptation to btc signet

[EthanYuan]

The btc signet has its own special definition of difficulty consensus, such as powLimit, which is different from both maintain and testnet.

In order to support btc signet spv with spv type contract, this pr will be realized by extending flags. Flags is the u8 data at the end of the spv client cells args.

The expanded Flags are as follows：

// Constants for the chain type flag
// Specifically utilizing the two highest bits for chain type identification
pub const FLAG_CHAIN_TYPE_MAINNET: u8 = 0b0000_0000; // for mainnet
pub const FLAG_CHAIN_TYPE_TESTNET: u8 = 0b1000_0000; // for testnet
pub const FLAG_CHAIN_TYPE_SIGNET: u8 = 0b0100_0000; // for signet

Compatibility Notes:

• For spv instance for testnet updated with this pr, spv service does not need to be upgraded.
• But for spv instance for signet to be deployed and updated, service needs to be updated to support signet as well (new pr will be submitted to service later)

---

Another modification is that POW should be checked regardless of chain type. Checking POW is the most important security for spv client on chain.

---

• CI needs to wait for the following data to be uploaded before it can be passed through：

• chore: add signet spv update tx test data ckb-bitcoin-spv-testdata#7

[Flouse]

TODO: update the comments of SpvTypeArgs.flags

ckb-bitcoin-spv/verifier/src/types/core.rs

Lines 90 to 95 in 8de163a

	/// Bit flags to control features.
	///
	/// From high to low:
	/// - Set 0-th bit to true, to disable difficulty checks.
	/// - Other bits are reserved.
	pub flags: u8,