Harper should attempt to detect mixing up "exacerbated" and "exasperated".

I was just reading the comments after watching a YouTube video and one was about the presenter mixing up "flouting" and "flaunting" - which we already have an issue about if not a linter yet - but also about mixing up "exacerbated" and "exasperated" - which I don't believe has come up here before.

It is covered in online discussions though.

Examples from GitHub and Stack Overflow:
- This problem is further **exasperated** if similar objects don't have an instance of a key or contain only one
- The problem is further **exasperated** by the lack of documentation from AWS about the limits on this particular endpoint
- I imagine a basic question that is **exacerbating** me.
- The child window within the menu seems to be the **exasperating** factor here.
- A few historic office buildings on key Chestnut blocks caught fire and were left in a state of disrepair for many years further **exasperating** the 'empty' feeling

Start by locating the existing word-confusion detection and its tests, then compare their handling with the examples in this issue. Add coverage for incorrect uses of “exacerbated” and “exasperated,” while checking that valid uses remain unaffected; done means the cited mix-ups are detected.

Written by the indexing model from the issue text.