Add --dry-run Option to ABACUS CLI

Background

The --dry-run option is a common feature in many CLI tools, which serves a critical role in operational safety and testing. This feature enables users to:

1、Preview changes: Users can see what changes a command would make without actually applying them. 2、Verify command syntax and parameters: Ensures that commands and the central input files are constructed correctly without the risk of disruptive impacts. 3、Integrate with scripts and automation: Allows developers to incorporate the CLI tool into larger scripts and workflows safely by testing them in a --dry-run mode first.

Describe the solution you'd like

I propose adding a --dry-run option to the command line interface. This option would allow users to simulate commands without actually making any changes to the system or data. Since INPUT, STRU, and KPT are the central input files for the ABACUS program, it is crucial to ensure that these files are configured correctly and stored in the working directory before executing the program. If there is an incorrect configuration in the INPUT, STRU, or KPT files, the tool should provide detailed error messages to help diagnose and fix the issues.The --dry-run option would be particularly useful for verifying that these files are correctly set up and ready.

Task list only for developers

[ ] Notice possible changes of behavior
[ ] Explain the changes of codes in core modules of ESolver, HSolver, ElecState, Hamilt, Operator or Psi

Notice Possible Changes of Behavior (Reminder only for developers)

No response

Notice any changes of core modules (Reminder only for developers)

No response

Notice Possible Changes of Core Modules (Reminder only for developers)

No response

Additional Context

No response

Task list for Issue attackers (only for developers)

[ ] Review and understand the proposed feature and its importance.
[ ] Research on the existing solutions and relevant research articles/resources.
[ ] Discuss with the team to evaluate the feasibility of implementing the feature.
[ ] Create a design document outlining the proposed solution and implementation details.
[ ] Get feedback from the team on the design document.
[ ] Develop the feature following the agreed design.
[ ] Write unit tests and integration tests for the feature.
[ ] Update the documentation to include the new feature.
[ ] Perform code review and address any issues.
[ ] Merge the feature into the main branch.
[ ] Monitor for any issues or bugs reported by users after the feature is released.
[ ] Address any issues or bugs reported by users and continuously improve the feature.

deepmodeling / abacus-develop