[fix] fix typo s/muiti-node /multi-node etc.

[digger-yu]

📌 Checklist before creating the PR

• [ ] I have created an issue for this PR for traceability
• [x] The title follows the standard format: [doc/gemini/tensor/...]: A concise description
• [x] I have added relevant tags if possible for us to better distinguish different PRs

🚨 Issue number

Not involved

📝 What does this PR do?

fix typo s/muiti-node /multi-node etc. detail info modified: applications/ColossalEval/colossal_eval/evaluate/gpt_evaluate.py modified: applications/ColossalMoE/train.py modified: applications/ColossalQA/colossalqa/data_loader/document_loader.py modified: applications/ColossalQA/colossalqa/local/colossalcloud_llm.py modified: applications/ColossalQA/colossalqa/local/llm.py modified: applications/ColossalQA/colossalqa/retrieval_conversation_universal.py modified: applications/ColossalQA/colossalqa/retriever.py modified: applications/ColossalQA/colossalqa/utils.py modified: examples/language/openmoe/model/modeling_openmoe.py modified: examples/language/openmoe/train.py

💥 Checklist before requesting a review

• [ ] I have linked my PR to an issue (instruction)
• [ ] My issue clearly describes the problem/feature/proposal, with diagrams/charts/table/code if possible
• [x] I have performed a self-review of my code
• [x] I have added thorough tests.
• [x] I have added docstrings for all the functions/methods I implemented

⭐️ Do you enjoy contributing to Colossal-AI?

• [x] 🌝 Yes, I do.
• [ ] 🌚 No, I don't.

Tell us more if you don't enjoy contributing to Colossal-AI.