Update `cspell.json` to ignore the text "Niven"

Prerequisites

Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page.
Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA guide.

Overview

We need to add the specified false positive term to the appropriate list in the Code Spell Checker configuration file cspell.json.

Action Items

[ ] You must use VS Code as your local text editor and install the Code Spell Checker extension. Code Spell Checker can be installed either using the VS Code text editor[^1] or the VS Code Marketplace website[^2].
[ ] Do not change any configuration settings or make any spell corrections.
[ ] Open the file cspell.json and locate the list named "ignoreWords": [ ]
[ ] Add / insert the text "Niven", on the first line of the list:
```
  "Niven",
```
[ ] Add to the front of the existing list- do not remove or replace any other list item.
[ ] Save cspell.json and then test the change by opening _data/external/_wins-data.json and confirming that no Code Spell Checker error/message related to "Niven" is displayed for this file.
[ ] Docker testing is not required. Create a Pull Request in the usual manner, with changes only to cspell.json.

Resources

[^1]: Installing Code Spell Checker from the VS Code text editor [^2]:Code Spell Checker - VS Marketplace

This issue was created as part of # 5312

Hi @t-will-gillis.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

t-will-gillis / website