Bug: Too many warnings in CI tests due to not converged `scf_thr`

[WHUweiqingzhou]

Describe the bug

I submit a PR about new mixing method #3226, many warning occurs.
After double-checking, I find all of them is caused by the reason that the ref-data is calculated by a too large scf_thr calculation.
I suggest we should update ref-data of CI-tests by using a quite small 'scf_thr', and remove warning and use fatal error only.

Maybe someone be interested about this?

Expected behavior

No response

To Reproduce

No response

Environment

No response

Additional Context

No response

Task list for Issue attackers (only for developers)

• Verify the issue is not a duplicate.
• Describe the bug.
• Steps to reproduce.
• Expected behavior.
• Error message.
• Environment details.
• Additional context.
• Assign a priority level (low, medium, high, urgent).
• Assign the issue to a team member.
• Label the issue with relevant tags.
• Identify possible related issues.
• Create a unit test or automated test to reproduce the bug (if applicable).
• Fix the bug.
• Test the fix.
• Update documentation (if necessary).
• Close the issue and inform the reporter (if applicable).

[WHUweiqingzhou]

Only PR which change mixing-related code would introduce warnings due to large scf_thr, maybe we do not worry about it for all PR. b.t.w., I still think we should remove warnings in CI tests.