[Move] Part-6 Classes into Different Library - Neo.Extensions

[cschuchardt88]

Description

Reorganized and move classes from neo library to neo.extensions library.

Fixed problems and warnings that occurred. Along with naming violations.

Change Log

• Moved methods from Neo.IO.Helper class
• Added BinaryReaderExtensions, BinaryWriterExtensions, MemoryReaderExtensions, SpanExtensions classes
• Added more methods to StringExtensions, ByteExtensions MemoryExtensions
• Added using statement
• Fixed unit tests

Type of change

• Optimization (the change is only an optimization)
• Style (the change is only a code style for better maintenance or standard purpose)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Unit Testing

Checklist:

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

[Jim8y]

I know that adding new methods will make it easier to do the work, and actually it wont cause any trouble, but please avoid doing so.

[shargon]

Agree, please don't add if the PR is so big and is not related with this

[shargon]

@superboyiii could you check if there are any storage change in both networks?

[superboyiii]

@superboyiii could you check if there are any storage change in both networks?

Sure

[superboyiii]

Mainnet test result shows it's compatible. I will try testnet as well.

[superboyiii]

Data is compatible on testnet as well.

addressed