943 certificate sign/verify EIP-55 **thor-devkit** compatibility

[lucanicoladebiasi]

Description

The code at packages/core/src/certificate/certificate.ts introduces

• the sign method to encapsulate the logic encoding a Certificate instance to its byte array representation;
• the verify method is compatible with the certificates built by with thor-devkit if the the certificate doesn't include text occurring in https://en.wikipedia.org/wiki/Unicode_equivalence ambiguities.

The tests at packages/core/tests/certificate/certificate.unit.test.ts

• include challenges certificates involving Unicode ambiguities;
• include tests to assure thor-devkit compatibility, those must be uncommented because the dependency from thor-devkit introduce an resolved lint rule not allowing the import of the bignumber.js library.

NOTE: The sign method is introduced to avoid ambiguities in the transformation of a certificate from object to its byte representation through JSON and UTF8 encoding and decoding. If no UTF normalisation is enforced, 'high' Unicode planes (ideograms, emoticons) are not consistently represented with the same bytes because the normalisation is demanded to the runtime.

Fixes # 943

• sign enforces UTF8 Normalization Form Canonical Composition to compute the signature.
• verify is insensitive about the signer address case (but the equivalent thor-devkit code is not).
• sign and verify functions ignores additional properties introduced if the certificate instance extends the Certificate interface: the signature is computed only on the basis of the properties defined in the Certificate interface.

Type of change

Please delete options that are not relevant.

• [x] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [x] yarn test:solo

Test Configuration:

• Node.js Version: v20.24.0
• Yarn Version: 1.22.22

Checklist:

• [x] My code follows the coding standards of this project
• [x] I have performed a self-review of my code
• [x] I have commented on my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] New and existing integration tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules
• [x] I have not added any vulnerable dependencies to my code

[github-actions[bot]]

Test Coverage

Summary

Lines	Statements	Branches	Functions
	100% (3404/3404)	100% (794/794)	100% (705/705)

Title	Tests	Skipped	Failures	Errors	Time
core	495	0 :zzz:	0 :x:	0 :fire:	1m 7s :stopwatch:
network	658	0 :zzz:	0 :x:	0 :fire:	4m 11s :stopwatch:
errors	48	0 :zzz:	0 :x:	0 :fire:	11.704s :stopwatch:

[lucanicoladebiasi]

Accurate revision with @rodolfopietro97 shows the introduction of thor-devkit dependency in test code messes lint behaviour. Lint configuration must be changed, a specific ticket will be assigned for the task. Rodolfo and I decided to proceed to promote this PR to review to include the fixes.