This reverts commit 049a58e7.

This reverts merge request !8189

This reverts commit b44f7ac1.

1. Make areRelated and relativeTerm work regardless of familyTesting.  This fixes some bugs right away, since they are already used unchecked a few places, and it makes it a lot easier to write generic descriptions and event text without breaking things.
2. Extend relativeTerm to handle sole parent and grandparent/grandchild cases.
3. Make relativeTerm return null instead of "some unknown blood relation" if no relationship could be found between two slaves.  This was never OK to output (i.e. "$his some unknown blood relation" doesn't read right), so it ended up just being tested for everywhere (which can be done more easily with null).
4. Remove duplicate code based on familyTesting when the only difference was whether areRelated and relativeTerm or their legacy alternatives were used.  There is a lot of this.
5. Remove hasRelationP entirely (it is superseded in all use cases by areRelated).

Split AdManager.tallySlave into two functions, one which does the actual tallying for the report, and a free function which counts the categories in which a slave matches a facility's ads.

Remove AdManager from everywhere that doesn't actually need to keep a slave tally state, and just use App.Ads.getMatchedCategoryCount everywhere the persistent state is not needed.  This means only App.Ads.report actually needs an AdManager instance, which cleans things up quite a bit.