ci(openapi): Add spell-check CI step and fix existing typos

[vdusek]

• Configure typos spell checker to check the repository.
• Add typos.toml config to ignore false positives.
• Fix all current typos.
• Relates: Ensure OpenAPI specs can serve as a reliable source of truth for typed client generation #2182

[apify-service-account]

Preview for this PR was built for commit 7faec0d and is ready at https://pr-2187.preview.docs.apify.com!

[fnesveda]

Cool 👍 Maybe this should also be discussed with @TC-MO, this is more in his yard.

[vdusek]

Cool 👍 Maybe this should also be discussed with @TC-MO, this is more in his yard.

Sure, I quickly looked at the current CI setup, and it seems that doc content has its own spell-check steps. Because of that, I configured typos to run only on the apify-api directory.

But of course, we can definitely enable typos for the whole repository, if @TC-MO agrees.

Running it across the repo showed a few existing typos, for example:

error: `ommitted` should be `omitted`
   ╭▸ ./sources/academy/platform/expert_scraping_with_apify/apify_api_and_client.md:52:25
   │
52 │     // fields should be ommitted
   ╰╴                        ━━━━━━━━
error: `extenison` should be `extension`
  ╭▸
1 │ ./sources/platform/integrations/images/airtable/airtable_search_apify_extenison.png
  ╰╴                                                                      ━━━━━━━━━
error: `accross` should be `across`
    ╭▸ ./sources/academy/webscraping/scraping_basics_javascript/08_saving_data.md:115:243
    │
115 │ …rom the syntax of JavaScript objects, but people now use it accross programming languages.
    ╰╴                                                             ━━━━━━━
error: `extenison` should be `extension`
   ╭▸ ./sources/platform/integrations/data-storage/airtable/index.md:42:18
   │
42 │ Search for Apify extenison and install it
   ╰╴                 ━━━━━━━━━
error: `programatically` should be `programmatically`
   ╭▸ ./sources/legal/latest/terms/store-publishing-terms-and-conditions.md:88:44
   │
88 │ 3. "**Pay per Event**" which allows you to programatically charge for events in your Actor source code. You need to pre-define the…
   ╰╴                                           ━━━━━━━━━━━━━━━
   error: `Plaftorm` should be `Platform`
   ╭▸ src/components/PlatformCard.jsx:24:7
   │
24 │ const PlaftormCard = ({ title, items }) => {
   ╰╴      ━━━━━━━━
error: `Plaftorm` should be `Platform`
   ╭▸ src/components/PlatformCard.jsx:39:16
   │
39 │ export default PlaftormCard;
   ╰╴               ━━━━━━━━
   
   ...

[TC-MO]

I'm fairly certain that we used this already before but retired it for one reason or another (not 100% sure atm). At the same time maybe the tool is better now or we could have better rules in place. I see no harm in setting this up for whole repo and trying it out. Worst case scenario we can revert to having it only work on apify-api

[apify-service-account]

Preview for this PR was built for commit 503c505 and is ready at https://pr-2187.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit 5487f4c and is ready at https://pr-2187.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit 122f204 and is ready at https://pr-2187.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit 57cefe1 and is ready at https://pr-2187.preview.docs.apify.com!