Create and port more test cases for Vector128<T> and Vector256<T>

[fiigii]

The new SIMD types Vector128<T> and Vector256<T> have been enabled in CoreCLR dotnet/coreclr#15244. We need more test cases to make sure they work well with other CoreCLR features.
Some language features have to be tested:

• try/catch
• typecast
• boxing/unboxing
• calling convention
• ref
• ...

CoreCLR already has certain such tests for System.Numeric.Vectors (e.g., VectorReturn) that can be ported to Vector128<T> and Vector256<T>.
This work may require more hardware intrinsic, we will implement them preferentially.

category:correctness
theme:testing
skill-level:intermediate
cost:small

[fiigii]

cc @jkotas @AndyAyersMS @CarolEidt @BruceForstall @tannergooding @benaadams @4creators

[4creators]

@fiigii

I would be interested in working on this issue, however, in the next 1 - 2 weeks I could allocate smaller part of my time due to time pressure from other work. If you think it is OK pls assign me to it

When do you plan to implement loading and storing intrinsics? They would be very handy for any tests.

[fiigii]

@4creators Thanks for your interest. I have no permission to assign issues, and this issue contains many test work for Intel hardware intrinsics. Please just go ahead to pick one test that you want to try when you get a chance. I will write more test cases as well.

When do you plan to implement loading and storing intrinsics? They would be very handy for any tests.

That is my next step work, I hope I can check in Load/Store intrinsics after the new year. Before that, you can use Unsafe.Read/Write instead.