[Neo VM Optimization] Detect reference counter miscalculation.

[Jim8y]

Description

This pr checks the stackitems being pushed to the stack only contains items that are on the stack.

Why is this problem?

We can literarily create stackitems at anywhere in the execition engine and push it to the evaluation stack, it is highly possible that we construct compound type stackitems that also contain compound type, then when we push it to the stack, only the first demension subitem will be added to the reference counter, the second/higher demonsion subitems will be ignored.

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

How Has This Been Tested?

• TestInvalidReferenceStackItem

Test Configuration:

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

[Hecate2]

if (!subItem.OnStack) is often triggered. The subitems are exactly not OnStack.

[shargon]

How can this happens in a real environment?

[Hecate2]

Now the tests can be passed, but I think nothing is really checked

[Jim8y]

How can this happens in a real environment?

will add ut tests, still working on it.

[vncoelho]

Too much HF and do not solve,as we discussed.
Do not merge for now.

[Jim8y]

With #3334 this is unnecesssary anymore