feat: support ckbfs uri

[code-monad]

This pull request introduces support for handling ckbfs:// URIs in the SDK, just like how it deal with BTCFS URI links.

The server(https://ckbfs.nvap.app/api) is open-sourced in: https://github.com/nervape/ckbfs-server, as anyone can deploy a copy.

the api accepts different forms of CKBFS URIs

• TypeID based, which uses the CKBFS's TypeID as uri identifier: ckbfs://bce89252cece632ef819943bed9cd0e2576f8ce26f9f02075b621b1c9a28056a
• Transaction based, uses ckbfs://{tx_hash}i{index}： ckbfs://431c9d668c1815d26eb4f7ac6256eb350ab351474daea8d588400146ab228780i0

you can check a testnet example:

• https://test-ckbfs.nvap.app/api/v1/ckbfs/compatible?uri=ckbfs://431c9d668c1815d26eb4f7ac6256eb350ab351474daea8d588400146ab228780i0
• https://test-ckbfs.nvap.app/api/v1/ckbfs/compatible?uri=bce89252cece632ef819943bed9cd0e2576f8ce26f9f02075b621b1c9a28056a

or a mainnet example:

• https://ckbfs.nvap.app/api/v1/ckbfs/compatible?uri=ckbfs://59775e63f8ef8b3a1650fb1ddeea7801f1e7ac5d160282d3ad2c801445401b22i0
• https://ckbfs.nvap.app/api/v1/ckbfs/compatible?uri=ckbfs://56831d51ab469eb7ee6551fd39e65caeff9b35569804a6532cf00f4c6f6e3d6a

And, you may want also check the non-compatible(with omiga's original api) version's output: https://ckbfs.nvap.app/api/v1/ckbfs?uri=ckbfs://56831d51ab469eb7ee6551fd39e65caeff9b35569804a6532cf00f4c6f6e3d6a

and also api to directly download the file https://ckbfs.nvap.app/api/v1/ckbfs?uri=ckbfs://56831d51ab469eb7ee6551fd39e65caeff9b35569804a6532cf00f4c6f6e3d6a&format=raw