feat: use type safe onion packet

[doitian]

Use type safe onion pack instead of Vec<u8>, which is error-prone since at some places we store PaymentOnionPacket, and at other places we may store PeeledPaymentOnionPacket.

[doitian]

The test case below will fail. @chenyukang can you help to debug? It seems that I have passed wrong parameters when forwarding the onion packet.

I also added channel_outpoint and next_hop to the struct TLC, because the current interface requires a PeeledPaymentOnionPacket to send the packet to the next hop.

cargo test fiber::tests::channel::test_send_payment_with_3_nodes -- --nocapture

[doitian]

The test case below will fail. @chenyukang can you help to debug? It seems that I have passed wrong parameters when forwarding the onion packet.

I also added channel_outpoint and next_hop to the struct TLC, because the current interface requires a PeeledPaymentOnionPacket to send the packet to the next hop.

cargo test fiber::tests::channel::test_send_payment_with_3_nodes -- --nocapture

Found the cause, the amount is not correct when creating outbounding tlc from the pending inbounding tlc.