Toolchain-2023.5-hotfix：LibRI, Libnpy and others link update

[QuantumMisaka]

• libri, libnpy version update
• mirror station in bohrium update
• more notice for libri, libcomm and libnpy in README and scripts

Reminder

• Have you linked an issue with this 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 #3223

What's changed?

• update version of Libnpy and LibRI
• update mirror dataset link
• update README and more information notice

[dyzheng]

Thanks for your contribution, can you help us to build auto test of toolchain?

[QuantumMisaka]

Thanks for your contribution, can you help us to build auto test of toolchain?

An easiest way to auto test is just using toolchain*.sh and build_abacus*.sh to build abacus, source abacus_env.sh and run this abacus in some example. This version of Toolchain turn-off deepks and libri option for default due to give user a better first-time usage, so this function may need to test in some specific way.

I consider that an ABACUS mirror (docker or others) with toolchain installation can be used for auto test ?

[QuantumMisaka]

Thanks for your contribution, can you help us to build auto test of toolchain?

I have viewed some auto test failure of toolchain, the problem is weird and should not happen in the newest version of toolchain. take intel toolchain as example, the toolchain usage is :

1. cd toolchain
2. sh toolchain_intel.sh
3. sh build_abacus_intel.sh (that's for default setting, which is NOT include deepks and LibRI in default NOW)
4. source abacus_env.sh

May this steps need check-out ?

[QuantumMisaka]

@caic99 @dyzheng If there is not any problem, can this link update PR be merged ?

[dyzheng]

Toolchain is very useful, thanks for your contribution.