Localization process isn't aligned with weekly releases

[TylerLeonhardt]

Due to the process change of weekly releases, the process for Localization of VS Code is broken.

A lot of it heavily relied on monthly branching:

https://github.com/microsoft/vscode-loc-drop/blob/2e9a289e57ba3111ea358f7399b91b2a256de82c/build/update-vscode-branch.yml#L4-L5

even in our previous process monthly release process, the branching was done by Endgame Champ.

Additionally, the pipeline relies on building VS Code in order to extract the strings from it... with VS Code moving faster, keeping those build steps stable will be difficult and has already given me headaches over the years.

With weekly releases this has to be rethought.

Ideas:

• Can we not do this branch swapping and run the pipeline off of either the current release branch or even main? (this will need to make sure that the engine version is properly reflected in the resulting language packs)
• Can we avoid building vscode in a satellite repo and instead bring this creation of English strings into Core and then pass them to a pipeline in vscode-loc-drop?

Since we are in a broken state today, this is quite important to address as it means no new strings are translated.

[jrieken]

Sorry, this might have gotten lost in the slimmer endgame plan. Tho, it is something we can easily add back but also any process simplification and cleanup is very welcomed

[joaomoreno]

@TylerLeonhardt I've always had trouble keeping the entire localization machinery in my head. So much so that I never really knew how it fully works. Please feel free to take the opportunity to dramatically simplify it! Inlining as much as possible to the core product build sounds like a great first step.

[TylerLeonhardt]

Ok so, given the importance of figuring this out quickly due to not getting new strings, I've made a short fix that doesn't make things worse and simplifies things a bit:

We now run this pipeline daily, which will check for the latest release/XXX branch, if there's a newer one, it will do what it did before and update the repo to track that new branch. This will bump the engine version so everyone's happy. This means that endgame champ no longer has to run a pipeline to do this. One less step ✅

This means that new strings will only go in when we branch, and with an SLA of 3 days, they may be slightly delayed before the release... but that's not too bad. I think it's ok. Plus, weekly releases, if a string doesn't make it, oh well, wait a week, it'll be there no problem. Not the end of the world.

Possible improvement of that: Release language packs when they change instead of on a schedule. That'll really be reactive... it's probably ok to do this, I think. ✅ microsoft/vscode-loc#2165

We still keep the same "mirroring of VS Code build steps" which isn't great but it's also what we had before so that's ok tracked: https://github.com/microsoft/vscode-loc-drop/issues/1357

[TylerLeonhardt]

Moving to 1.113 for verification to give localization some extra time to propagate the new strings.