feat: batch support for domain registration

[julianmrodri]

• Decode domain names when processed in Batch. This requires processing the internal transactions of the TX data field, using RLP and following the FifsRegistrar encoding.)
• Add support and configuration for the RNS Batch Registration contract (in all environments).
• Test for transaction decoding in Batch Mode (Registering two domains).

[jurajpiar]

🚀 Looking good

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
4 Code Smells

No Coverage information
0.0% Duplication

[AuHau]

I have taken the liberty to do small refactor for some style tweaks as I did not find any critical problems.

I have few general remarks though:

• please don't force push once a PR is reviewed, it makes it hard to track the incremental changes for the reviewer
• use camelCase for variable naming (batchprocess vs batchProcess)
• if you want to write a comment for function use JSDoc (see example here

One more thing that we should generally improve. Whenever there is some "magic" thing that cannot be deduced from the codebase itself, there should be an exhaustive comment on why it is what it is. For example when you have name = Utils.hexToAscii('0x' + domainData.slice(218, domainData.length)) you should explain why do you slice from 218 (for example what is the format of the hash/data etc.). Similarly, why do you decode the Batch registration in the way you do.

The problem here is that if somebody who does not have a clue what is this about comes to the code, he won't have any idea what is going on. In my experience, this can be even you once you come back to the code in a month or two, after you moved to do some other thing, so it is generally good to have it there. We can add it in separate PR, so it does not block the release.