feat: add support for multiple data script outputs when creating a token

[pedroferreira1]

Motivation

A use case needs to create tokens with data script outputs (more than one in the same create token transaction, if possible). This is similar to the Create NFT transaction, however we would be marking this token as an NFT in our metadata bucket, which is bad for the use case.

Because of that, we decided to add support to data script outputs in the lib methods adding them in the last positions of outputs, because the NFT standard expects the data output to be in the first output.

This is a short term solution and a new project will be created to define better how to better identify an NFT token, without fixing where the data output must be.

Acceptance Criteria

• Add support for one or many data script outputs in a token create transaction.
  • This token can't be identified as an NFT by our wallet service lambda.
• Change getNFTCreationFee method name to getDataScriptOutputFee.
  • Even though this is a breaking change and not critical for the new feature, this improves the method name.
• The method to create NFT continues accepting only one data script output, so we don't change the method signature.

Security Checklist

• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

[codecov]

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (fcc08f6) 78.76% compared to head (8ed6944) 78.77%.

Files	Patch %	Lines
src/utils/tokens.ts	81.81%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #596      +/-   ##
==========================================
+ Coverage   78.76%   78.77%   +0.01%     
==========================================
  Files          68       68              
  Lines        5383     5386       +3     
  Branches     1144     1145       +1     
==========================================
+ Hits         4240     4243       +3     
  Misses       1126     1126              
  Partials       17       17              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[r4mmer]

question(if-minor): Do you think we should have the string be encoded?

For NFTs we used utf8 encoding since the data would be a string anyway, but now that we are allowing other types of data output should we have a different encoding, for instance base64 since its safe for utf8 strings and binary data.
Even if we keep using utf8 I think we should add the expected encoding on the docstrings, to make sure the caller knows how to pass the data.

[pedroferreira1]

As discussed privately, we will keep the utf-8 encoding for now (added the info in the docs 8ed6944) and discuss this support in another issue (#597)

[r4mmer]

issue(if-minor): This may be used by the other wallets.

If it is being used we should remember to bump the lib and make this change on the wallets after this is released

[pedroferreira1]

I thought we would be using it in the wallets but we actually don't. We have method in the wallet utils but we should change to use the lib.

https://github.com/HathorNetwork/hathor-wallet/blob/master/src/utils/tokens.js#L111