Add support for inclusive language linting

**What problem does this solve?**
Documentation and technical writings now requires use of inclusive language. This will be useful for such cases.

**Proposed Solution**
It can be optional feature with flag --inclusive like [textlint](https://textlint.org/) (textlint-rule-alex in it)

**Examples**
The ~~master~~ primary server ~~controls~~ manages all the ~~slave~~ reference nodes, this configuration works ~~best for everyone~~ well for most people.

**Component**
- [x] Core engine
- [x] Plugin/Extension
- [ ] Other: _____

**Additional Context**
See [alexjs](https://alexjs.com/) and [woke](https://getwoke.tech/) for demo

The issue proposes an optional --inclusive flag for the core engine or a plugin/extension and references textlint-rule-alex, alexjs, and woke. No files, tests, or entry points are named, so first inspect the existing CLI and plugin architecture and discuss the rule scope with maintainers. Done should include an agreed implementation path, documented behavior, and tests for the supplied examples.

Written by the indexing model from the issue text.