add production GEMM tests

[matthiasdiener]

Description

Add production-like GEMM tests for Qwen3 and Deepseek3.

Type of change

• Documentation change (change only to the documentation, either a fix or a new content)
• 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)
• Infra/Build change
• Code refactoring

Changes

Please list the changes introduced in this PR:

• add a new test suite for production-like GEMM tests for Qwen3 and Deepseek3.

Checklist:

• I have read and followed the contributing guidelines
• The functionality is complete
• 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

[alextmagro]

nit: I think break should go on its own line for readability here.

[matthiasdiener]

Thanks, done in 77f1c45

[ipanfilo]

Please write the changes description. Also, why production LLM shapes cannot be added to existing gemm test?

[matthiasdiener]

Please write the changes description.

Added, thanks.

Also, why production LLM shapes cannot be added to existing gemm test?

My thinking was that we can run just these particular tests "standalone", without the other GEMM tests, on (say) a new architecture, for testing.

[ipanfilo]

Please write the changes description.

Added, thanks.

Also, why production LLM shapes cannot be added to existing gemm test?

My thinking was that we can run just these particular tests "standalone", without the other GEMM tests, on (say) a new architecture, for testing.

It the difference is only in usage, can it be added just with different prefix or as different suite: INSTANTIATE_TEST_SUITE_P(OperatorTest, GEMMTestSuite) so they can easy be run separately ?