Feature/value updater

[tznind]

Proposed Changes

Added new service UpdateValues which propagates changes (e.g. ECHI mapping changes) throughout the deployed database tables.

Types of changes

What types of changes does your code introduce? Tick all that apply.

• Bugfix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that would cause existing functionality to not work as expected)
• Documentation-Only Update (if none of the other choices apply)
  • In this case, ensure that the message of the head commit from the source branch is prefixed with [skip ci]

Checklist

By opening this PR, I confirm that I have:

• Reviewed the contributing guidelines for this repository
• Ensured that the PR branch is in sync with the target branch (i.e. it is automatically merge-able)
• Updated any relevant API documentation
• Created or updated any tests if relevant
• Accurately updated the CHANGELOG
  • NOTE: This must include any changes to any of the following files: default.yaml, any of the RabbitMQ server configurations, GlobalOptions.cs
• Listed myself in the CONTRIBUTORS file 🚀
• Requested a review by one of the repository maintainers

[lgtm-com]

This pull request introduces 1 alert when merging e4fa254 into 8515f05 - view on LGTM.com

new alerts:

• 1 for Dereferenced variable may be null

[rkm]

Looks great, thanks.

We'll need to update the RabbitMQ configs and architecture diagrams once we have the other bits of this pipeline in place, but this PR is good for now.

[lgtm-com]

This pull request introduces 1 alert when merging 897d317 into 8515f05 - view on LGTM.com

new alerts:

• 1 for Dereferenced variable may be null