fix: use the default links per block for importing file

[alvin-reyes]

Changes

I noticed that the dag builder generates a different cid when from IPFS.

This PR will use the same default number of links per block configuration on the dag builder which will make it par with IPFS/Kubo.

I have tested it with several files and it works as expected. @en0ma please test this against your files as well.

[10d9e]

LGTM

[en0ma]

@alvin-reyes It did not work for me

outputs from the same files;

• Estuary (this branch) - bafkreif376h46qwktu3bgxxvwrkqftqjjryqnm5dpbfz5kqr5jzvewtcgu
• Kubo (ipfs add the_file -cid-version=1) - bafybeifpyygt45smwbigangoabvqv7roweq7qruucnqd63r4ihxiyfrwfi

[gmelodie]

@alvin-reyes I got both equal and different CIDs. The difference seems to be when the file is larger in size. For instance I got different CIDs for rockyou.txt:

estuary: bafybeihedpf2eftaa5bqcqfz7jd6tfnxwabxanhkc5o4ortgx3yxtgtb6a
ipfs: bafybeicyij7pqmzohg5ndc2kl2z445me52gufm5gx4ncd747pzqi7rbgxe

but the same for pinning.go:

bafkreic3uqrhu72hdl4nm6nrc37q6plb7x2xtmbtcj6724fywqaf25udu4

[alvin-reyes]

I realized that we don’t need to change the way we compute our CIDs since it’ll work either anyway. We encountered a weird behaviour last week where in the CIDs are different from the ones uploaded on api.estuary.tech and on shuttles.

I think @en0ma already fixed this on his commit (e.i revert the logic to dump the content to the blockstore).

I think it’s safe to close this one for now.