Add length check to getLisk32AddressFromPublicKey

[Phanco]

What was the problem?

This PR resolves #9083

How was it solved?

Added length check to getLisk32AddressFromPublicKey

How was it tested?

Unit test updated

[codecov]

Codecov Report

Merging #9124 (8559d8f) into release/6.1.0 (185e3fa) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@              Coverage Diff               @@
##           release/6.1.0    #9124   +/-   ##
==============================================
  Coverage          84.34%   84.35%           
==============================================
  Files                652      652           
  Lines              23966    23970    +4     
  Branches            3489     3490    +1     
==============================================
+ Hits               20215    20219    +4     
  Misses              3751     3751           

Files	Coverage Δ
elements/lisk-cryptography/src/address.ts	96.55% <100.00%> (+0.12%)	⬆️
elements/lisk-cryptography/src/constants.ts	100.00% <100.00%> (ø)

[Phanco]

In lisk-sdk, lisk-cryptography is exported earlier than lisk-framework. Hence this element could not retrieve the constant from lisk-framework and I afraid it will be too risky to re-arrange the exports just for this purporse. So I defined the constant locally at lisk-cryptography

[sitetester]

In lisk-sdk, lisk-cryptography is exported earlier than lisk-framework. Hence this element could not retrieve the constant from lisk-framework and I afraid it will be too risky to re-arrange the exports just for this purporse. So I defined the constant locally at lisk-cryptography

Each package should be independent of SDK, hence each package should have it's own constant.

[sitetester]

elements/lisk-cryptography/test/address.spec.ts

Currently, there are describe blocks starting with #. For future PRs, this practice should be discouraged, as there is no such standard