Modify tests to distinguish between emit- and interpreted-based invoke

[steveharter]

As a follow-up to #67917, explicitly support testing of both emit-based and interpreter-based invoke.

No functional changes made to the Release build. The invoke-based tests will run twice, and thus be indirectly tested under both emit and interpreter.

The Checked and Debug runtime builds however support passing in 2 new binding flags to use either the emit or interpreter-based invoke. These do not actually change the public System.Reflection.BindingFlags enum but do apply a soft reservation on that enum for those 2 values to support these test scenarios in an explicit and stable manner.

[ghost]

Tagging subscribers to this area: @dotnet/area-system-reflection
See info in area-owners.md if you want to be subscribed.

Issue Details

---

As a follow-up to #67917, explicitly support testing of both emit-based and interpreter-based invoke.

No functional changes made to the Release build. The invoke-based tests will run twice, and thus be indirectly tested under both emit and interpreter.

The Checked and Debug runtime builds however support passing in 2 new binding flags to use either the emit or interpreter-based invoke. These do not actually change the public System.Reflection.BindingFlags enum but do apply a soft reservation on that enum for those 2 values to support these test scenarios in an explicit and stable manner.

Author:	steveharter
Assignees:	steveharter
Labels:	area-System.Reflection, test-enhancement
Milestone:	7.0.0

[steveharter]

Closing; taking a different approach using context switches.