Strict check for given messages count and originally revealed

[anton-iskryzhytskyi]

Description

• [x] Tests for the changes have been added (for bug fixes / features)
• [x] The commit message(s) follow conventional commits
• [ ] Documentation has been added / updated (for bug fixes / features)
• [x] Changes follow the contributing document.

Motivation and Context

The main point of this PR is to restrict providing more messages to the blsVerifyProof than it was revealed originally. For now it is possible to provide all revealed + signed messages in the right order and then add to the messages array some additional, not signed, not revealed messages and receive a successful response result.verified === true. More details in the issue

Does this PR introduce a breaking change?

• [ ] Yes
• [x] No

Which merge strategy will you use?

• [x] Squash
• [ ] Rebase (REVIEW COMMITS)

[tplooker]

@anton-iskryzhytskyi thanks for this contribution!