[Bug] Auto detect framework upgrade's dependency on a specific binary version

# 🐛 Bug

Changes in Move that require a framework upgrade might have dependencies on changes in the VM. We want to automate discovering this dependency if possible to avoid cases where we do a framework upgrade without the VM changes being rolled out first.

Having tests that cover specific features might help but in many cases, these tests might be skipped or don't have coverage of all possible cases. It'd still be helpful to have auto detection when we attempt a release where there's a dependency on a binary that is not yet released to sufficient validator nodes.