Probes in modules have undefined properties when accessed through nested modules

The probe's configure script is still actually run, and it sets its own properties fine, just that they are not accessible from within the containing module if that module is instantiated from a dependency from another module.

If the module is directly depended on, everything works fine.