[Optimize]: Murmur128 is a noncryptographic hash aglorithm

[Wi1l-B0t]

Description

Same as the murmur32, murmur128 is a noncryptographic hash aglorithm.
So it shouldn't be implemented as a cryptographic hash (This would be misleading.):

This PR:

1. Implements murmur128 as a noncryptographic hash aglorithm;
2. Optimizes murmur128 performance in some cases;

A simple benchmark:

Before:

.NET SDK 9.0.203
  [Host]     : .NET 9.0.4 (9.0.425.16305), Arm64 RyuJIT AdvSIMD
  DefaultJob : .NET 9.0.4 (9.0.425.16305), Arm64 RyuJIT AdvSIMD


| Method    | Mean     | Error    | StdDev   |
|---------- |---------:|---------:|---------:|
| Murmur128 | 81.65 us | 1.461 us | 1.295 us |

After:

.NET SDK 9.0.203
  [Host]     : .NET 9.0.4 (9.0.425.16305), Arm64 RyuJIT AdvSIMD
  DefaultJob : .NET 9.0.4 (9.0.425.16305), Arm64 RyuJIT AdvSIMD


| Method                | Mean     | Error    | StdDev   |
|---------------------- |---------:|---------:|---------:|
| Murmur128_ComputeHash | 40.74 us | 0.097 us | 0.090 us |

Fixes # (issue)

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

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

[Copilot]

Pull Request Overview

This PR implements a noncryptographic version of the Murmur128 hash algorithm and optimizes its performance while updating the associated tests and helper methods.

• Implements Murmur128 as a noncryptographic hash algorithm by deriving from NonCryptographicHashAlgorithm.
• Refactors the hash calculation to use a new Append/ComputeHash pattern with improved tail handling.
• Updates tests and helper extensions to reflect the new API and improved performance.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
tests/Neo.UnitTests/Cryptography/UT_Murmur128.cs	Test adjustments to use the new ComputeHash method and HashSizeInBits.
src/Neo/Cryptography/Murmur128.cs	Refactor of the Murmur128 implementation to optimize performance and tail processing.
src/Neo/Cryptography/Helper.cs	Update Murmur128 extension methods to use ReadOnlySpan-based implementation.
benchmarks/Neo.Benchmarks/Benchmarks.Hash.cs	Introduction of a benchmark for the Murmur128 performance.

[Copilot]

[nitpick] Consider refactoring this loop to use an index-based iteration instead of repeatedly slicing the source span. This may help reduce overhead in performance-critical paths.

[shargon]

@Wi1l-B0t Copilot is right, avoiding coy the array and using index it will be faster

[Wi1l-B0t]

@Wi1l-B0t Copilot is right, avoiding coy the array and using index it will be faster

The source is a span. Slice is fast.