Rename "prepare" script to "curate" to prevent auto-runs

The `prepare` script is run when the repository is installed. On top of
creating issues when the repository is set as dependency in another
project for some reason, as described in:
#789 (comment)

... this also seems wrong because:
1. There is no guarantee that the curation will run without errors. A patch
may no longer apply for instance.
2. Projects may want to depend on the raw data and may not need to run the
curation and package preparation logic at all.

This update replaces the "prepare" script with a "curate" one, explicitly
called in the jobs that need it.

Author: tidoust

.github/workflows/curate.yml

@@ -34,10 +34,12 @@ jobs:
         # the curated branch
         fetch-depth: 0
 
-    - name: Prepare curated and packages data
-      # Note that "ci" runs the "prepare" script
+    - name: Install dependencies
       run: npm ci
 
+    - name: Prepare curated and packages data
+      run: npm run curate
+
     - name: Test curated and packages data
       run: npm run test
 

.github/workflows/test.yml

@@ -10,7 +10,11 @@ jobs:
     - uses: actions/setup-node@v2
       with:
         node-version: '14'
-    - run: npm ci
-    - run: npm test
+    - name: Install dependencies
+      run: npm ci
+    - name: Prepare curated and packages data
+      run: npm run curate
+    - name: Test curated and packages data
+      run: npm test
 env:
   FORCE_COLOR: 3

package.json

@@ -41,7 +41,7 @@
   },
   "scripts": {
     "create-patch": "node tools/create-patch.js",
-    "prepare": "node tools/prepare-curated.js ed curated && node tools/prepare-packages.js curated packages",
+    "curate": "node tools/prepare-curated.js ed curated && node tools/prepare-packages.js curated packages",
     "test": "mocha --recursive",
     "test-css": "mocha --recursive test/css",
     "test-elements": "mocha --recursive test/elements",