[branch rebase] rebase main to Feature/resize_embedding (#5554)

[flybird11111]

• fix

• [release] update version ([release] update version hpcaitech/ColossalAI#5411)

• [hotfix] fix typo s/keywrods/keywords etc. ([hotfix] fix typo s/keywrods/keywords etc. hpcaitech/ColossalAI#5429)

• [devops] fix compatibility ([devops] fix compatibility hpcaitech/ColossalAI#5444)

• [devops] fix compatibility

• [hotfix] update compatibility test on pr

• [devops] fix compatibility

• [devops] record duration during comp test

• [test] decrease test duration

• fix falcon

• [shardformer] fix gathering output when using tensor parallelism ([shardformer] fix gathering output when using tensor parallelism hpcaitech/ColossalAI#5431)

• fix

• padding vocab_size when using pipeline parallellism

padding vocab_size when using pipeline parallellism

fix

fix

• fix

• fix

fix

fix

• fix gather output

• fix

• fix

• fix

fix resize embedding

fix resize embedding

• fix resize embedding

fix

• revert

• revert

• revert

• [doc] release Open-Sora 1.0 with model weights ([doc] release Open-Sora 1.0 with model weights hpcaitech/ColossalAI#5468)

• [doc] release Open-Sora 1.0 with model weights

• [doc] release Open-Sora 1.0 with model weights

• [doc] release Open-Sora 1.0 with model weights

• [doc] update open-sora demo ([doc] update open-sora demo hpcaitech/ColossalAI#5479)

• [doc] update open-sora demo

• [doc] update open-sora demo

• [doc] update open-sora demo

• [example] add grok-1 inference ([example] add grok-1 inference hpcaitech/ColossalAI#5485)

• [misc] add submodule

• remove submodule

• [example] support grok-1 tp inference

• [example] add grok-1 inference script

• [example] refactor code

• [example] add grok-1 readme

• [exmaple] add test ci

• [exmaple] update readme

---

📌 Checklist before creating the PR

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

🚨 Issue number

Link this PR to your issue with words like fixed to automatically close the linked issue upon merge

e.g. fixed #1234, closed #1234, resolved #1234

📝 What does this PR do?

Summarize your work here.
if you have any plots/diagrams/screenshots/tables, please attach them here.

💥 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
• I have performed a self-review of my code
• I have added thorough tests.
• I have added docstrings for all the functions/methods I implemented

⭐️ Do you enjoy contributing to Colossal-AI?

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

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