🐛 Updated stripe prices/products table population

refs https://github.com/TryGhost/Team/issues/591
refs ffe24a728c

It's possible to have sites which still have customer subscriptions in their DB from old Stripe accounts, most likely added when we allowed Stripe Direct, as those subscriptions were not cleaned up. While populating stripe prices and products for existing subscriptions, we want to ignore these old subscriptions which are not part of current Stripe account instead of throwing error and halting the one off migration which we currently do.

The population script will re-run again as long as no new subscriptions are created between the last release and this, and there were no old invalid plans in DB, which is a very unlikely edge case so the data will eventually re-populate correctly.

package.json

@@ -58,7 +58,7 @@
     "@tryghost/kg-mobiledoc-html-renderer": "4.0.0",
     "@tryghost/limit-service": "0.4.2",
     "@tryghost/magic-link": "1.0.2",
-    "@tryghost/members-api": "1.3.0",
+    "@tryghost/members-api": "1.3.1",
     "@tryghost/members-csv": "1.0.0",
     "@tryghost/members-ssr": "1.0.2",
     "@tryghost/mw-session-from-token": "0.1.19",

yarn.lock

@@ -567,10 +567,10 @@
     jsonwebtoken "^8.5.1"
     lodash "^4.17.15"
 
-"@tryghost/members-api@1.3.0":
-  version "1.3.0"
-  resolved "https://registry.npmjs.org/@tryghost/members-api/-/members-api-1.3.0.tgz#8792328144b8855fb44298bbd198e8f7ff21a454"
-  integrity sha512-vXGwYivpLjxbZoPES1UL0awvh+ag87kt5F7aFx++qUKKaxxoIA9OFdKgDnuFfYi5S1jv++nA2C9HZ6pzTkcJzg==
+"@tryghost/members-api@1.3.1":
+  version "1.3.1"
+  resolved "https://registry.npmjs.org/@tryghost/members-api/-/members-api-1.3.1.tgz#5afba6a797b33f226561b5d3f772693b24e2dfc0"
+  integrity sha512-PRVYaEcajtARoVNjvngBSb+2q1R875E1anqzXAmJ7M+kPsAh3ZdsNhFJnTb7wwMFdzuwhjMrNEl7/5iCOXRJUQ==
   dependencies:
     "@tryghost/errors" "^0.2.9"
     "@tryghost/magic-link" "^1.0.2"