Recipe repository updates do not propagate during M-x straight-pull-all

[raxod502]

Let us consider the following situation:

1. User runs M-x straight-pull-all
2. MELPA is updated, changing the recipe for package X from A to B
3. Package X is updated

However, in step 3 the recipe A is used rather than the recipe B. This is confusing and violates the principle of least surprise. We should change something.

[progfolio]

#576 can be used programmatically to pull recipe repositories first.

[raxod502]

That is an improvement, but unfortunately it does not fully solve the problem. The reason is that, while pulling a recipe repository updates the recipes on disk, we actually need to re-run recipe resolution to propagate the changes into memory. It's also not just a matter of doing special-case lookups after pulling a recipe repository, because we need to handle inheritance correctly. I think the most appropriate way to solve the problem, aside from forcing a reload of the init-file (which seems rather bad), is to record a list of the exact sequence of calls to straight-use-package during init. Then we can simply replay them whenever we want, without forcing a reload of the init-file.