Refactor: use less memory and optimize performance to calculate force and stress in pw base

[dyzheng]

I have refactored stress code structure in this PR.
In case Mg16Al16, the memory cost of stress calculation from 16752 MB to 194 MB.

Linked Issue

Close #3714
Close #4158
Close #3710
Close #4026
Close #3931
Close #4031

Unit Tests and/or Case Tests for my changes

• A unit test is added for each new feature or bug fix.

What's changed?

• Example: My changes might affect the performance of the application under certain conditions, and I have tested the impact on various scenarios...

Any changes of core modules? (ignore if not applicable)

• Example: I have added a new virtual function in the esolver base class in order to ...

[Qianruipku]

Has the efficiency of the new algorithm been tested? Are there any test data available?

[dyzheng]

Has the efficiency of the new algorithm been tested? Are there any test data available?

I have not tested many cases, in Mg16Al16 case , time of stress_nl change from 94 s to 124 s, I think the performance of new method still can be improved.

[Qianruipku]

Perhaps the QE code can be used as a reference.

[dyzheng]

I will work with @grysgreat to accelerate performance in GPU/DCU, change this PR to draft.

[mohanchen]

two general comments. 1) lack of doxygen-style notes or explanations. 2) both CPU and GPU codes, especially for the GPU codes, are not well-written in terms of high-performance computing (but this can be improved in future)