Ensure localization changes are ported to release/8.0

[ericstj]

I believe our localization process feeds changes back into main and not release branches. I think we'll need to port these PRs as appropriate to release/8.0.

I'd be curious how other dotnet repos handle this to see if we can follow their lead. @wtgodbe any learnings from aspnetcore?

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

---

I believe our localization process feeds changes back into main and not release branches. I think we'll need to port these PRs as appropriate to re release/8.0.

I'd be curious how other dotnet repos handle this to see if we can follow their lead. @wtgodbe any learnings from aspnetcore?

Author:	ericstj
Assignees:	-
Labels:	area-Infrastructure-libraries, blocking-release
Milestone:	8.0.0

[ericstj]

@cristianosuzuki77 pointed me to some good docs on this. https://github.com/dotnet/arcade/blob/main/Documentation/OneLocBuild.md#if-youre-releasing-from-a-branch-other-than-main-including-servicing-branches shows how to enable loc for our release branch.

We should do this for release/8.0 (and make that a regular thing when we do these snaps during RC moving forward).

@carlossanlop can you please pick this up?

Note: this may be blocked by #90466 if the same break is present in release/8.0.

[wtgodbe]

I'd be curious how other dotnet repos handle this to see if we can follow their lead. @wtgodbe any learnings from aspnetcore?

We don't have a strict process for this either, we do manual backports as necessary. I wouldn't be surprised if we were missing some loc changes in release branches because of this - thanks for bringing this to my attention