route53 : no changes to the yaml trigger an update on route53 zone

[purehyperbole]

When rds_instances or clusters are used as a target for an route53 entry, applying the same yaml with no changes triggers an update when it should not.

[purehyperbole]

Looks to be an issue with the template variable generated from the "new" build being diffed with the "actual" value stored from the last build. Given that the values field on the internal component stores both user values and templated values, it might require a breaking change to fix this.