Handling recursive objects

[pagbabian-splunk]

Related issue: 996

There have been sightings of a few objects where recursion could take place and in general there are no bounds on recursion. There may be value in a is_recursive keyword when authoring an object to warn tools (e.g. the class graph feature) not to attempt to resolve ad infinitum the possible paths.

Note, not all recursion is direct, e.g. ldap_person has a manager which is a user which in turn has an ldap_person hence it should be noted at the first level that a potential recursion could occur.

Further, having a documented recursion limit could be an option, e.g. recursion_limit = 2 so that things don't get out of hand.