Automotive: The version upgrades work off the app version number so this won't work.

The VersionMigrationsJob logic works off the app version number, but Automotive requires a bigger version number than the app so it is set to a large number. For example it is the current production:

App version: 7.19.2
Google Play version: 7566
Automotive version: 57566
Buildkite build: 7366

Here is an example of the code:

```
if (previousVersionCode < 377) {
deletePodcastImages()
}
if (previousVersionCode < 422) {
addUpNextAutoDownload()
}
```

Start by locating VersionMigrationsJob and trace how previousVersionCode is obtained and compared with the app, Google Play, Automotive, and Buildkite version values shown here. The issue is resolved when migrations no longer rely on the app version in a way that fails for Automotive; the payload does not name a test or a specific replacement strategy.

Written by the indexing model from the issue text.