refactor: dynamic value handling

[roleyfoley]

Intent of Change

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves the structure or operation of the implementation)
• New feature (non-breaking change which adds functionality)

Description

• Moves to detecting dynamic value replacement requirements using regex instead of split based pattern matching
• Changes type handling for replacement values to only support string based replacements ( if number or bool returned then convert to string )
• Moves replacement miss handling to the invoke function instead of requiring the dynamic value handlers to manage missing values
• Moves occurrence dynamic value replacement to support subOccurrences along with occurrences
• Adds baseline dynamic value provider to perform lookups of baseline components

Motivation and Context

This was all found during the troubleshooting of an issue where a number based attribute in a replacement was causing the entire value to be replaced. While troubleshooting this I found a number of issues along the way that this resolves.

• No error responses when a value isn't quite right
• SubOccurrence's wern't working as the occurrence passed to the resolution was always the parent
• The removal of the OPSDATA_BUCKET default var as this is no longer a default and is provided by baseline

How Has This Been Tested?

Tested locally

Related Changes

Prerequisite PRs:

• None

Dependent PRs:

• None

Consumer Actions:

• None