Board versions for 3.2.x can be accidentally downgraded to 3.1.x

For obvious reasons, all board versions need an effectively installed check.

Currently none of the 3.1.x migrations have this, while the 3.2.x one's do.

The result of that is anytime the 3.1.x is version incremented, it has the possibility to change a 3.2.x board's version back down to the 3.1.x version.