Separate dict.txt from clever-rockies to distinguish terminology from method

[dax-westerman]

The following is an idea I wanted to get down as a potential process improvement. It's also an example of what could be included as part of a "Project" to bucket ideas.

---

Currently the dict.txt file containing the terminology is strongly bound to the clever tool. It might make sense to separate the dict.txt file into its own repository to gain the following benefits.

• Versioning of terminology independent of code changes to CLEVER
• Code to update/validate dict.txt contained as distinct from CLEVER (separation of concerns, method versus validation)
• Prevents accidental inclusion of code changes, since PR review may focus solely on terminology (reduction of human error)

The "main" version of the dictionary could be included as a git submodule (i.e., reference to a git repo within a git repo), such that CLEVER will maintain a reference to the "production" version of the terminology.