When featureCompatibilityVersion is 3.2, a 3.4 node can't initial sync decimal data

If the primary has featureCompatibilityVersion 3.4, and during initial sync, we copy over decimal data before copying admin.system.version, then we reject the decimal data, and the initial sync fails.

We would also like to successfully initial sync from a primary with featureCompatibilityVersion 3.2 that has decimal data, since a user can get into this state by inserting decimal data and then setting featureCompatibilityVersion to 3.2.