Feat/comms module/reference data

[morgang-adappt]

Description

This PR allows Reference Data to be used in Email Notifications. The flow for configuring a reference data dataset follows the same process used in dashboards, with variable mapping used to pass query variables. This includes reusing the existing dashboard filters configuration. The values entered into the form inputs created in the dashboard filters configuration are saved and loaded for Email Notification edition.

An additional change to support this implementation is dynamic date filters for Reference Data. The tokens {{today}}, {{today±n}}, {{now}}, and {{timeLastExecuted}} are replaced in the email function app with their corresponding values before querying. This enables scenarios provided by the client that are dependent on the scheduler and reference data.

Useful links

• Please insert link to ticket
• Please insert link to back-end branch if any
• Please insert any useful link ( documentation you used for example )

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

These changes have been tested by our internal QA team following scenarios provided by the client.

Screenshots

• Reference Data selection and variable mapping in dataset configuration

• Existing dashboard filters configuration used in dataset configuration to configure form inputs for variable mapping.

• Form inputs from dashboard filter in dataset configuration (which persist and load values across Email Notification editions and triggers)

• Send separate email field configuration for Reference Data using JSONPath expression.

Dependencies

• The function app now requires ENCRYPTION_KEY added to its environment variables, this is the same key used on the backend to encrypt API configuration settings.

Checklist:

• * I have set myself as assignee of the pull request
• * My code follows the style guidelines of this project
• * Linting does not generate new warnings
• * I have performed a self-review of my own code
• * I have put the ticket for review, adding the oort-backend team to the list of reviewers
• * I have commented my code, particularly in hard-to-understand areas
• * I have put JSDoc comment in all required places
• * My changes generate no new warnings
• * I have included screenshots describing my changes if relevant
• * I have selected labels in the Pull Request, according to the changes with code brings
• I have made corresponding changes to the documentation ( if required )
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules