Bug fix: interceptAnyObject used in monitorAPI

[ShirShintel]

Bug Description

shell.getAPI returns empty objects for several APIs even though real implementation was contributed.

Problem

When the repluggable host is created with the disableMonitoring option off, monitorAPI is used to intercept and monitor any function in the API. This is done by contributing an intercepted API object instead of the contributed API. The intercepted API object is created using interceptAnyObject, that recursively intercepts all functions in the nested object and wraps them with monitoring logic.

The problem is that interceptAnyObject assumes the API is a plain object, as can be seen by its type. When passed an API that is not a plain object (e.g. a function), _.mapValues returns an empty object and the API implementation is lost.

The assumption that API is a plain object is wrong: APIs are not obligated to be built using a plain object, and can be really anything, from objects to functions to primitives. This can be seen in the TAPI type that makes no assumptions of the shape of the API.

Solution

1. Changed the type of the inner argument in interceptAnyObject to be any, and instead added a type guard to make sure we only intercept plain objects.
2. Replaced the _.isObjectLike check with _.isPlainObject which is more restrictive (will return false for arrays, maps, etc)
3. Added sanity tests