Update terminology used in the wiki

[jrfnl]

As discussed in #1908, the wiki pages should be reviewed and references to "whitelisting" code should be replaced with other phrasing, such as "ignoring code"

The wiki should also be updated to reflect that support for the old-style WPCS native ignore comments has been removed in WPCS 3.0.0.

[jrfnl]

List of things which will need updating in the wiki before the 3.0.0 release:

• [x] Running in Travis - the workflow will need to be changed to not clone the repos, but use a Composer install.
• [x] Customizable sniff properties - references to removed sniffs should be moved to the bottom with a note that those sniffs are no longer available in WPCS 3.0+.
• [x] Customizable sniff properties - the names of custom properties which have been renamed/changed/added will need to be updated.
• [x] whitelist code that is being flagged with errors - page probably should be removed (or rewritten)
• [x] Update references to the project from WPCSto WordPressCS (and if that changes URLs, make sure links to those wiki pages in the README and such get updated too).

Note: this list may not be complete....

[dingo-d]

Running in Travis - the workflow will need to be changed to not clone the repos, but use a Composer install.

We will leave this for legacy reasons? Since we're not running checks in TravisCI any more 🤷🏼‍♂️

[jrfnl]

We will leave this for legacy reasons? Since we're not running checks in TravisCI any more 🤷🏼‍♂️

This is not about our CI, but an example for projects using WPCS. There may still be (mostly commercial plugins/themes) running their CI on Travis, so for them, it's good to have an example for how to set it up.

[jrfnl]

Wiki pages review list - those pages marked with a ✔️ have been updated for WordPressCS 3.0.0:

• [x] Home
• [x] Sidebar
• [x] Customizable sniff properties
• [x] Fixing errors for input data
• [x] Sanitizing array input data
• [x] Escaping a WP_Error object
• [x] Ignoring Parts of a File
• [x] Running in GitHub Actions
• [x] Running in Travis
• [x] Setting up WordPressCS to work in Atom
• [x] How to use WPCS with Eclipse and XAMPP
• [x] Setting up WordPressCS to work in Sublime Text
• [x] Upgrade Guide to WordPressCS 2.0.0 for Developers
• [x] Project Timeline

New pages to be added:

• [x] Upgrade guide to WordPressCS 3.0.0 for end-users/ruleset maintainers.
• [x] Upgrade guide to WordPressCS 3.0.0 for Developers of external standards.

[jrfnl]

All pages have received a cursory review and been update. Further, more detailed review is welcome, but not essential for the WPCS 3.0.0 release.

Closing this issue now as fixed.