bug: vftables are needed for each class inherited in its hierarchy, not just immediate bases

[sei-eschwartz]

There is a bug in reasonVFTableBelongsToClass: https://github.com/cmu-sei/pharos/blob/master/share/prolog/oorules/rules.pl#L947

The problem is that a class needs a vftable for each class inherited in its hierarchy. So if class A inherits from B, which inherits from C and D, then A needs at least two vftables, even though it only directly inherits from one class.

This first came to light in #187.

[sei-eschwartz]

This is resolved in #214

[edmcman]

pharos/share/prolog/oorules/rules.pl

Line 947 in e14b16e

% Constructors may inline embedded constructors. If non-offset