Datamigration for new Fulfillment type feature

[sujithvn]

Resolves #6472
Impact: breaking
Type: feature

This PR is replaced by #6633

Issue

Migrate data to the new format required for the new FFT plugins

Solution

We have 3 stages in a single migration;

• Copies over the existing Shipments & FlatRateFulfillmentRestrictions collections to Fulfillment & FulfillmentRestrictions collections respectively
• Updates the Fulfillment collection with the newly introduced fields (fulfillmentType & fulfillmentMethod). Since the existing user base had only Shipping/Flatrate as the fulfillment type/method till date, we would be using those values to update collection
• update the Groups collection with the new permissions

Breaking changes

The 2nd stage above handles the breaking change where we would be using the possible existing values as the values or newly introduced fields.

Testing

In an existing installation, perform the data-migration. Update the installation to use the new version having fulfillment types. All activities in admin/shop (related to Products/Orders/FF-types/Catalogs/Carts) should continue to work without issues

To test migration steps, install api-migrations package and include the below entry in the migrator.config.js file.

export default {
  tracks: [
    {
      namespace: "fulfillment",
      package: "../reaction/packages/api-plugin-fulfillment",
      version: 2
    }
  ]
};

Run the command:
MONGO_URL=mongodb://localhost:27017/reaction npx migrator migrate

[changeset-bot]

⚠️ No Changeset found

Latest commit: 81bde07

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[zenweasel]

A few changes needed here

[zenweasel]

This just adds them to shop manager and owner which is fine if they used the Out of the Box permissions and made no changes, but what it actually should do is add it to any group that has the old equivalent permissions?

[sujithvn]

@zenweasel

When we say "any group that has the old equivalent permissions", does it mean any group which would have the same entries in the array as of shop-manager and owner?

If the user has made a minor add/remove of any entry, then how do we decide whether that groups has to be considered or not?

[sujithvn]

@zenweasel
As discussed, I have made the code change to update 'any' group that has the permissions.
As per the change, we are checking each group for any of the old permissions (related to shipping) and inserting the corresponding individual FFT permissions (using a mapper) in all of the impacted groups.

[sujithvn]

This PR is replaced by 6633
#6633