Expose helpers as shared module and usable while writing custom code

I am working on a private extension at the moment and I noticed that the core extension already provides specific helpers methods that I would like to reuse as sharedModules and as helpers when I wrote custom code in rule and data elements.

I am interested in the following helpers:
* getObjectProperty https://github.com/adobe/reactor-extension-core/blob/master/src/lib/helpers/getObjectProperty.js
* textMatch https://github.com/adobe/reactor-extension-core/blob/master/src/lib/helpers/textMatch.js
* valueComparison https://github.com/adobe/reactor-extension-core/blob/master/src/lib/conditions/valueComparison.js
* variable https://github.com/adobe/reactor-extension-core/blob/master/src/lib/conditions/variable.js

I am aware that variables and valueComparison are both linked to specific conditions but it would be ideal to move them to helpers.

Ideally once exposed the use will be:
* when writing private extensions use turbine.getSharedModule('core', 'getObjectProperty'); to reuse in code to avoid writing similar code for same purpose
* in configuration add an option to expose helpers to window._satellite.helpers.getObjectProperty to reuse in custom code section in Adobe Launch rules and data elements

Start by reading the listed helper and condition entry points: src/lib/helpers/getObjectProperty.js, src/lib/helpers/textMatch.js, src/lib/conditions/valueComparison.js, and src/lib/conditions/variable.js. Trace how shared modules and custom code are exposed, then verify that the requested helpers can be used through turbine.getSharedModule('core', ...) and window._satellite.helpers without duplicating their implementations.

Written by the indexing model from the issue text.