Version-specific model builds in Hub

[berekuk]

Right now buildRecentModelRevision worker uses runSquiggle, which uses the latest dev Squiggle.

We should use the selected Squiggle version instead, with versioned-components.

[berekuk]

Note: this is complicated for dev ("Next" version) builds:

• potentially, we want to use dev builds as a smoke test for the upcoming Squiggle version, so, if we have enough CPU capacity, we might want to trigger builds for all existing Squiggle Hub models on latest dev Squiggle
• when combined with Cache and expose serialized build values #3499, serialization format or Squiggle behavior can change, so we can't just show the cached version; serialized version from the previous dev build might not render correctly with the latest dev code

The solution is to expose the git revision from squiggle-lang, and use it as a key for dev versions.