Remove oneDNN-specific attributes from matmul

[Silv3S]

PR types

Others

PR changes

OPs

Describe

In #49515 each fuse done for matmul and matmul_v2 was converted to be executed as fused_matmul. Fusion logic was extracted to dedicated fused op and fused kernel. As base matmul is now not fused with anything, all extra attributes can be deleted from OPMaker, .pbtxt file and unit tests.

Changes done in this PR:

• Remove fusion logic from base matmul op and kernel,
• Remove placeholders for empty attributes in unit tests,
• Remove test_matmul_mkldnn_op.py unit tests, which has extra attributes hardcoded in base operators. These test cases are covered in test_onednn_matmul_transpose_reshape_fuse_pass.py and test_onednn_reshape_transpose_matmul_fuse_pass.py. Same for matmul_v2.

[paddle-bot]

你的PR提交成功，感谢你对开源项目的贡献!
请关注后续CI自动化测试结果，详情请参考Paddle-CI手册。
Your PR has been submitted. Thanks for your contribution!
Please wait for the result of CI firstly. See Paddle CI Manual for details.

[Silv3S]

reshape_transpose_matmul_mkldnn_fuse_pass introduced 4 extra oneDNN-specific attributes for matmul op: fused_reshape_X, fused_reshape_Y, fused_transpose_X, fused_transpose_Y. Then in #30011 checkpoint with only one of these attributes (fused_reshape_Y) was added to op version registry.

Now, we are going to delete all oneDNN-specific attributes from base ops. Do you think we could just delete this checkpoint and restore matmul version 0 or new checkpoint should be added and matmul would be version 2 then? @YuanRisheng, @chenwhql please advice

[yaomichael]

@YuanRisheng please help review, approve and merge

[Silv3S]

@zhangting2020 could you please approve removing decorator @skip_check_grad_ci? I deleted test cases with extra hardcoded attributes from test_matmul_mkldnn_op.py as they are already covered in test_onednn_matmul_transpose_reshape_fuse_pass.py.

[Silv3S]

@XiaoguangHu01 could you please approve exceeding limit of 20 modified files?

[zhangting2020]

LGTM.

[XiaoguangHu01]

LGTM