fix: continue on buildRecord error

[BobVanB]

Improve Error Handling in submitChanges Function

Issue

Previously, when an error occurred while fetching zones in submitChanges, the function would return immediately, halting all processing. This prevented subsequent changes from being applied, even if they were unrelated to the failure.

Changes

• Modified the function to collect errors instead of returning immediately when fetching zones or processing changes.
• If a failure occurs, it is logged and added to a slice of errors, but the function continues processing the remaining changes.
• After iterating through all changes, the function returns a combined error list if any errors were encountered.

Impact

• Ensures that one failed change does not block others from being processed.
• Provides better visibility into multiple failures in a single run.
• Prevents unnecessary disruptions in external-dns behavior.

Discussion Point

Should we log and collect all errors, or are there specific cases where an immediate failure (return) is preferable?

[k0da]

LGTM