Feature: init_chg hr for initializing charge density with hrs1_nao.csr

[dyzheng]

Reminder

• Have you linked an issue with this pull request?
• Have you added adequate unit tests and/or case tests for your pull request?
• Have you noticed possible changes of behavior below or in the linked issue?
• Have you explained the changes of codes in core modules of ESolver, HSolver, ElecState, Hamilt, Operator or Psi? (ignore if not applicable)

Linked Issue

Fix #6792
hrs1_nao.csr file is large, test case should be designed to reduce memory, will be updated later.

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 ...

[mohanchen]

if you write the code in 'before_all_runners', then you don't need to specify if(istep==0) because it only be called once. If you write the code in 'before_scf', that's the wrong place to put the code.

[mohanchen]

Next, if you want to have a function to read density matrix from DMR, then the details (from line 174-211) are suggested to put into other functions, not in esolver_ks_lcao.cpp

[dyzheng]

I need to modify the operation of initializing the charge density such that the charge density is calculated after reading in the Hamiltonian or the density matrix, while skipping the original initialization strategy that starts from the atomic charge density.

[dyzheng]

However, due to the code coupling relationship, I do not wish to introduce dependencies on LCAO-related modules into the Charge module. Given that the charge density initialization strategy in the Charge module includes a charge density normalization operation, I must ensure that the charge density initialization is completed before performing the normalization. Therefore, the new initialization code must be placed prior to init_scf, which means the initialization of the Hamiltonian and the density matrix also needs to be moved before init_scf. This approach is feasible, but the program does require refactoring to achieve greater rationality and neatness. Owing to time constraints, I have not yet considered this issue in detail.