fix(localize): ensure extracted messages are serialized in a consistent order

[petebacondarwin]

The CLI integration can provide code files in a non-deterministic
order, which led to the extracted translation files having
messages in a non-consistent order between extractions.

This commit fixes this by ensuring that serialized messages
are ordered by their location.

Fixes #39262

[petebacondarwin]

@AndrewKushnir / @clydin - this will change the ordering of extracted messages in serialized files. But I think that since the order was non-determinate via the CLI integration previously, then this is arguably not a breaking change. WDYT?

[AndrewKushnir]

Thanks for the fix @petebacondarwin 👍 Just left a few minor comments.

[AndrewKushnir]

Thanks for updates @petebacondarwin 👍

this will change the ordering of extracted messages in serialized files. But I think that since the order was non-determinate via the CLI integration previously, then this is arguably not a breaking change. WDYT?

Given that the order was not consistent before, I think this should not be a breaking change. One potentially breaking aspect is that we now use first duplicate message in JSON translation file (vs the last one), but since Ivy i18n extraction pipeline is not the default one and JSON format was not documented yet, I'd not consider this change as breaking.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}