Restore variables in config-remote-sync

[ilyakuz-db]

Changes

When config-remote-sync patches YAML files with remote changes, it now restores variable references rather than always hardcoding values. This prevents configs from losing ${var.X} references after UI edits.

Note: There is a lot of ambiguity in how to restore the variables, because it's not always clear what the user's intent is, and this is hard to describe with a simple heuristic. In this PR, we make a best-effort deterministic attempt as a first step.

Supported use cases:

1. If any field that contains a variable was changed, and new values match this variable, we restore it. Safe guard
2. string template /bundle/${bundle.target}/{var.foo} case is also supported
3. new list item of the same type is added (job param / job task) -> if variables are used in existing items , and the field value matches the variable, we use this variable

Why

Improve the config-remote-sync experience for customers. We have received feedback that customers usually have their job parameteres defined as variables, and this PR aims to address some gaps there

Tests