Move provider tests to onnxruntime_provider_test and enable use of plugin EPs

[edgchen1]

Description

Move provider-specific unit tests that were formerly in onnxruntime_test_all to a new test program, onnxruntime_provider_test. Notably, this includes the op tests which test different provider implementations.

Enable some tests in onnxruntime_provider_test (those using ModelTester or OpTester) to use a plugin EP. The plugin EP usage is specified at runtime, so it is referred to as "dynamic". The dynamic plugin EP configuration can be specified with environment variable ORT_UNIT_TEST_MAIN_DYNAMIC_PLUGIN_EP_CONFIG_JSON.

This is an example value for ORT_UNIT_TEST_MAIN_DYNAMIC_PLUGIN_EP_CONFIG_JSON. The test infrastructure will register the plugin EP library at path/to/example_plugin_ep.dll. The op tests will use a plugin EP instance with the name example_ep.

{
  "ep_library_registration_name": "example_ep",
  "ep_library_path": "path/to/example_plugin_ep.dll",
  "selected_ep_name": "example_ep"
}

Motivation and Context

Enable use of plugin EPs in some provider-specific unit tests.

Notes for Reviewers

• There are many modified files but most of the changes are just #include path updates.
• I suggest setting the diff view to ignore whitespace changes.

[TedThemistokleous]

Hey , just seeing this now @edgchen1 @snnn.

The MIGraphX was using the pai_test_launcher.sh script in our CI so this has caused a build break for MIGraphX. We typically sync weekly to your Mainline and build against Onnxruntime to ensure MIGraphX EP builds off your main won't cause breaks. |

Is there something else we should be using now here instead? Should we just run the test launcher directly? From what I can tell, it seems like the Onnxruntime_test_all binary still exists I think we just need to add a filter for excluded tests still?

Is there a larger change here for builds/testing that we need to incorporate in our infrastructure? If so please let me know

[edgchen1]

Hey , just seeing this now @edgchen1 @snnn.

The MIGraphX was using the pai_test_launcher.sh script in our CI so this has caused a build break for MIGraphX. We typically sync weekly to your Mainline and build against Onnxruntime to ensure MIGraphX EP builds off your main won't cause breaks. |

Is there something else we should be using now here instead? Should we just run the test launcher directly? From what I can tell, it seems like the Onnxruntime_test_all binary still exists I think we just need to add a filter for excluded tests still?

Is there a larger change here for builds/testing that we need to incorporate in our infrastructure? If so please let me know

Sorry. I didn't find any existing usages in the repo, so I assumed it was fine to delete. You can add it back if you want.

The main change is to move some tests from onnxruntime_test_all to a new test program, onnxruntime_provider_test. To get the same test coverage, you'd want to also run the new test program. You may need to adjust your test filters accordingly, e.g., if they match a test that got moved.

[TedThemistokleous]

Good to know. Sure I can add that back in but if I can just call in the same piece, I can adjust CI directly then if this is the case.

[TedThemistokleous]

I think this was used when there was MIGraphX EP/ROCm EP CI but that got removed recently and we're in the process of adding it back