Given the switch to non-free license, we should either replace Redis with a FLOSS fork in Vagrant, or drop usages of it entirely.

Production MediaWiki only uses Redis for LockManager, and will probably replace that with a different cache as well. Vagrant uses it as the main object cache, main stash, session cache, job queue, ORES cache and DonationInterface cache (but not LockManager). Most of those could probably be replaced with Memcache and bring Vagrant closer to production. For the job queue, we could try to imitate production and use Kafka (and take the DX hit as the MediaWiki-Kafka integration is only half-implemented), or just use the DB job queue maybe. The Redis-based job queue doesn't seem to be working reliably anyway, and it's harder to debug than the DB-based job queue.