Re: "Where is the value in moving to an equivalent?"
Agreed on the general sentiment (prod vs. test), but I think it's worth remembering there are variations and levels of both.
That is, "prod" at some places might barely qualify as "test" in others, plus the reverse situation. Horses for courses.
Various analysis articles of the Broacom+VMware strategy, both pre- and post- buyout, theorized that Broadcom's plan is likely to keep the big-dollar big-contract "enterprise" customers locked-in, and maybe best-effort the rest. Reasoning is simple enough: the big customers are higher revenue, and probably less able to migrate away from VMware -- hard to change course on the Titanic, and all that.
Whereas the smaller outfits might be better equipped to migrate, more tolerant of test/dev foibles, and thus more willing to try other solutions. E.g. I ran a dev lab on a handful of vanilla KVM-qemu hypervisors, on boring last-year's model bare metal, no bells or whistles. The engineers carried on with it fine -- they were only interacting with VM's we spun up for them anyway -- and saved us a little money to offset some of the very expensive vmware license packs. Would I have wanted to run a prod database with failover shared-storage etc. that way? Not a bit. But for mostly ephemeral and generic VM's for developer types to (ab)use until they needed a new one or a different OS etc., it worked out.
The prod stuff stayed on VMware, and it was fine too. Though I wouldn't expect it'll stay there forever.
And that's the thing: I don't expect this is a long-term winning strategy for Broadcom, and I suspect they know that. So Broadcom are wringing out whatever profits they can get for as long as they can, and maybe VMware eventually follows some of the other Broadcom acquisitions.