Things needing updates if we were to change the Chapel name

In today's TSC meeting, we had a brief discussion about some things that would need to change if we were to change the name of the Chapel project. The following is a list that started out as an internal-to-HPE issue, reflected here to support the TSC's conversation. It may not be complete, and we encourage others to add comments on things we may have overlooked.

I'm breaking this into two lists: One that assumes that if we chose a "C" name (e.g., CatCowCan), the chpl abbreviation could still be used by file extensions, tool names, etc. if we called it the "C[atCowCan] High Productivity Language" (say). The second lists things that would need to change if 'chpl' couldn't still be retained.

I'm confident things are missing from these lists. If you come up with things, please add them in comments.

`chpl` OK
========
* English mentions of "Chapel" in documentation (spec, primers, users guide, website, …)
* github org & repo names (`chapel-lang`, `chapel`, `chapel-www`, `chapel-blog`, `chapel-vscode`, `sphinxcontrib-chapel`, …)
* website's domain name (`chapel-lang.org`)
* social media account names (X, BlueSky, LinkedIn, Mastodon, YouTube, …)
* community forum names and/or URLs (Discourse, Discord, Reddit, Gitter?, …)
* tool names:
* `c2chapel`
* `chapel-py`
* …?
* third-party deployments of software:
* homebrew formula
* DockerHub page / package
* Spack package
* E4S releases
* module name on Cray/HPE systems
* entries in HPE's software deployment frameworks
* attempt this online (ATO)
* …
* ChapelCon
* name of VSCode extension
* names of syntax highlighting extensions that are published separately
* vim
* emacs
* highlightjs
* pygments
* CLBG highlighter
* GitHub syntax highlighting / language identification tag (e.g., )
* StackOverflow tag and wiki page
* CLBG website entries
* Wikipedia entry
* RedMonk / Tiobe language ranking entries
* learnXInYMinutes entry
* trainings developed by others (e.g., Alexei Razoumov)
* Arkouda's website, docs, Spack dependencies, …
* names of associated projects when spelled out (CHapel Optimization Project, CHapel Multiphysics Software, …)
* HPE Developer pages / HPE Developer blog tags

`chpl` not OK
===========
* `chpl` compiler name
* and things that invoke it in our code base—test scripts, Makefiles, documentation, …
* `.chpl` file extension
* tool names:
* `chpl-language-server`
* `chplcheck`
* `chlpdoc`
* `chplspell`
* `chpltags`
* `chplvis`
* `printchplenv`
* …
* names of some compiler/tool flags
* `--print-chpl-home`
* `--html-chpl-home`
* `--print-chpl-settings`
* `--print-chpl-loc`
* …
* `CHPL_` prefix on environment variables
* `chpl__` prefix on module symbols (or not… are they all internal anyway?)
* names of associated projects when abbreviated (Chop, CHAMPS, …)
* Makefiles invoking the `chpl` compiler (e.g., Arkouda, CHAMPS, …)

Of course, beyond these lists, there is also:
* the task of retraining the world to use the new name rather than the old (e.g., people name-dropping us on reddit conversations, comparing to us in related work, mentioning us in blogs or talks, …)
* the large number of published papers, talks, videos that mention Chapel that can't/shouldn't be updated