Add parameter mapping feature

[zanete]

Why: Sub of #761 - so that we can automatically add the return values of one plugin to the inputs array under the name required by another plugin

What: Build a feature in IF that maps a parameter that is present in the input data to a new name that is expected by a particular plugin. For example, let's say a hypothetical plugin, myPlugin expects to see cpu/util in the inputs array. That p[recise parametr is not available in the array, but the precise same information is available with the cpu-utilization name. In this case, we want to use the mapping feature to pass the value of cpu-utilization to myPlugin as cpu/util.

The configuration for this should be done in the manifest, in the initialization bock for each plugin, for example:

initialize:
  plugins:
    my-plugin:
      method: MyPlugin
      path: @grnsft/dummy-plugins
      mapping:
        cpu/util: cpu-utilization

In this case, my-plugin, which expects to see cpu/util will understand that it should use the cpu-utilization values rather than throwing an error because cpu/util is not available.

Scope of work:

• Implement mapping feature
• Add unit tests

Acceptance criteria

• mapping feature allows re-keying data in the inputs array for the purpose of executing an individual plugin
  GIVEN the feature is implemented
  WHEN I run the following manifest:

name: sum
description: successful path
tags:
initialize:
  plugins:
    sum:
      method: Sum
      path: "builtin"
      global-config:
        input-parameters: ["cpu/energy", "network/energy"]
        output-parameter: "energy"
      mapping:
        cpu/energy: energy-from-cpu
        network/energy: energy-from-network
tree:
  children:
    child:
      pipeline:
        - sum
      config:
        sum:
      inputs:
        - timestamp: 2023-08-06T00:00
          duration: 3600
          energy-from-cpu: 0.001
          energy-from-network: 0.001

THEN IF should map the available energy-from-cpu and energy-from-network values to the expected cpu/energy and network/energy values and correctly execute the sum plugin, yielding the following manifest:

name: sum
description: successful path
tags:
initialize:
  plugins:
    sum:
      method: Sum
      path: "builtin"
      global-config:
        input-parameters: ["cpu/energy", "network/energy"]
        output-parameter: "energy"
      mapping:
        cpu/energy: energy-from-cpu
        network/energy: energy-from-network
tree:
  children:
    child:
      pipeline:
        - sum
      config:
        sum:
      inputs:
        - timestamp: 2023-08-06T00:00
          duration: 3600
          energy-from-cpu: 0.001
          energy-from-network: 0.001
      outputs:
        - timestamp: 2023-08-06T00:00
          duration: 3600
          energy-from-cpu: 0.001
          energy-from-network: 0.001
          energy: 0.002

This behaviour should generalize to any plugin.

[zanete]

@manushak @narekhovhannisyan please review ac to confirm you're ok with it

[zanete]

caution, this contains breaking changes. review needed from @narekhovhannisyan and @jmcook1186

[zanete]

need to update unit tests for plugins

[zanete]

the current solution causes breaking changes for plugin, so we are changing the function to be backwards compatible (work also without mappings)

[zanete]

@narekhovhannisyan @jmcook1186 please review 🙏