[OpCode Benchmark] add benchmark files

[Jim8y]

Description

This pr adds opcode benchmark files to ease the further work.

Fixes #

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

[nan01ab]

Gooood job!

[shargon]

I can't see anything beneficial if none of them contain a valid test, lots of classes that do nothing are not worth much (in my opinion)

[Jim8y]

@shargon we are working on benchmarking all of them, creating them one by one is unnecessary so I use script to create all of the files since we will otherwise create them one by one. This is benchmark, please dont use core-standard to review them.

[Jim8y]

I do empty files for

• 1, make it easier for you to review, since it contains no actual logic in those files,
• 2, easier for us to work, no need to create those files manually, and avoid missing opcodes.

[Jim8y]

I will fill those files with basic one opcode tests to make sure it is effective.

[shargon]

Ok, i will approve it when it's reqdy to review

[roman-khimov]

Many instructions require some setup before they can be tested, so in its current form this doesn't make much sense. Better merge real tests instruction after instruction (more likely sets of those).