The `lib/rules.js` file contains a code path that was previously needed to load core rules, but is no longer used as of aa56247.

This removes the undocumented `rules` property from `Linter` instances, as part of the effort to remove undocumented API surface from `Linter` (also see #9161). Config processing now exclusively uses `Linter`'s public API when defining rules. As a side-effect, the rule map utility in `lib/rules.js` no longer needs to access the filesystem, so we can remove the odd code generation logic from the browserify build.

…#11336)

This updates the `eslint:recommended` config to be generated dynamically rather than being hard-coded, to reduce the number of places that need to be kept up to date when core rules are added.

… (#11338)

* New: Allow globals to be disabled/configured with strings (fixes #9940)

As described in #9940, this allows globals in a config file to be specified with the strings `readable` and `writeable` rather than `false` and `true`, respectively. It also adds a new value, `off`, which turns off a previously-enabled global.

* Update lib/linter.js

Co-Authored-By: not-an-aardvark <[email protected]>

* Update docs/user-guide/configuring.md

Co-Authored-By: not-an-aardvark <[email protected]>

* Add test for "writable"

* Remove unnecessary map/destructuring

* Adjust confusing variable name

* Move note about legacy booleans down

…#11307)

This matches the way other formatters handle pluralization, which
seems simple enough to not require an additional package.