Precision of wavefunction file WFC_NAO_K*/LOWF_K_*.txt needs refactor

[kirk0830]

Describe the Code Quality Issue

one should aware that double can only reach precision like 1e-15, but now the file will have 25 decimal digits.
If the data will be needed in serious calculation later, why use non-binary format? If it is for human to read, why so many digits which even exceeds the precision of double?

Additional Context

No response

Task list for Issue attackers (only for developers)

• Identify the specific code file or section with the code quality issue.
• Investigate the issue and determine the root cause.
• Research best practices and potential solutions for the identified issue.
• Refactor the code to improve code quality, following the suggested solution.
• Ensure the refactored code adheres to the project's coding standards.
• Test the refactored code to ensure it functions as expected.
• Update any relevant documentation, if necessary.
• Submit a pull request with the refactored code and a description of the changes made.

[kirk0830]

@pxlxingliang Hi, could you solve this issue? cuz I am afraid that abacustest related workflows are sensitive to this

[pxlxingliang]

Yes, I will refactor the output of wavefunction recently.