Background jobs are referencing crates/versions by name instead of ID

[Turbo87]

Current Behavior

Some of our background jobs (e.g. sync_crate_feed) are referencing crates (and sometimes versions) by names. This can cause issues when crates are deleted and later reregistered while a background job is still in the queue.

Expected Behavior

Background jobs should use crate/version IDs instead of names to avoid these issues, since the IDs will always be unique.

Steps To Reproduce

No response

Environment

No response

Anything else?

This is not much of an issue in practice since regular crate deletions block re-registrations for 24 hours and within that timeframe the background jobs should have finished. It's still worth fixing though...

[Turbo87]

note that for logging purposes it might still be useful to also keep the crate name in the the background job payload.

the migration to primarily use IDs would probably need two deployment steps:

1. add crate_id: Option<i32> fields to the background jobs and ensure they are always filled when enqueuing new jobs
2. after that was deployed and no old jobs are in the queue anymore, change the field to crate_id: i32 and start using the field instead of the crate name.

[YohDeadfall]

@rustbot claim

[rustbot]

Error: The feature assign is not enabled in this repository.
To enable it add its section in the triagebot.toml in the root of the repository.

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #t-infra on Zulip.