Adds "IDEs" and "IDE's" to spelling list

What does this MR do?

!163070 (merged) is causing us to use the words IDEs (multiple) and IDE's (possessive), and they're being flagged as spelling issues.

The problem: the JetBrains extension isn't just for a single IDE - it's for all of the language-specific IDEs (hee hee, see what I did there) they offer. Crucially, it vastly simplifies the first step in instructions, because the name of this menu item changes depending on which IDE you're using at the time:

This allows something like On the top menu bar, select your IDE's name, then select **Settings**.

Thoughts?

Related issues

• Related to JetBrains extension: port over external docs (!163070 - merged)
• Related to https://gitlab.com/gitlab-org/editor-extensions/meta/-/issues/110+ which is the overarching work

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product availability details under the H1 topic title.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.