Disable OneLoc build temporarily

[hoyosjs]

It's currently blocking the official build.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[ericstj]

Can we just close the PR it's trying to update instead?

[ericstj]

I see that's what @mmitche did here: #61274

[jonfortescue]

Yeah, it looks like it has since started working just fine again: #61680

[safern]

Yes, we can close this PR now. Thanks @hoyosjs

[ericstj]

So this probably happened because @safern's PR changed the files here : #61489

Some thoughts on process:

1. When a loc PR comes in, merge so long as it's green and doesn't break the product.
2. Ideally this should be made easier by LOC system not churning the PR with empty commits.
3. If commits are required to make the LOC PR green or not break the product, those commits should be made to the LOC PR. If the LOC system sees a commit that is not itself as head of the PR branch it should not touch that branch and either just create a new PR, or skip creating a PR.
4. If a LOC PR has translation issues that don't break the product we should merge the LOC PR with those and either file issues, or open a PR to address them.

4 is something we can do now. I think 2 & 3 require changes to the loc build process.

[jonfortescue]

@ericstj I've brought up 2 & 3 with the loc team so hopefully those get rolled out soon.