[CI][lint] Add rule codespell back (#6236)

### What this PR does / why we need it?
After removing codepsell a while, we discovered that typo had a problem
correctly recognizing certain misspelled words, so I suggested adding it
back.

- vLLM version: v0.14.1
- vLLM main:
d68209402d

---------

Signed-off-by: wangli <wangli858794774@gmail.com>

.github/CODEOWNERS

@@ -29,7 +29,7 @@
 /.readthedocs.yaml  @wangxiyuan @Yikun
 /README*  @wangxiyuan @Yikun
 
-# exmaple
+# example
 /examples @wangxiyuan
 
 # tests

.github/ISSUE_TEMPLATE/110-user-story.yml

@@ -18,7 +18,7 @@ body:
       A brief introduction about the background of your use case, like your scenario, hardware size etc.
 - type: textarea
   attributes:
-    label: Bussiness Challenges
+    label: Business Challenges
     description: >
       Tell us how what kind of challenge you faced in this user story.
 - type: textarea
@@ -30,7 +30,7 @@ body:
   attributes:
     label: Extra Info
     description: >
-      Any extra infomation you want to include in this story
+      Any extra information you want to include in this story
 - type: markdown
   attributes:
     value: >

.github/workflows/_schedule_image_build.yaml

@@ -139,7 +139,7 @@ jobs:
             quay.io/ascend/vllm-ascend
           # Note for test case
           # https://github.com/marketplace/actions/docker-metadata-action#typeref
-          # 1. branch job pulish per main/*-dev branch commits
+          # 1. branch job publish per main/*-dev branch commits
           # 2. main and dev pull_request is build only, so the tag pr-N-openeuler is fine
           # 3. only pep440 matched tag will be published:
           #    - v0.7.1 --> v0.7.1-openeuler