Add and standardize paranext-core scripts

[myieye]

My paranext-core repo was way out of date, so npm install in the extension repo messed with the package lock file.

It felt awkward to have to switch directories in order to update the paranext-core repo, so good ol' AI added some useful scripts for me/us.

It made sense to prefix them all with core:, which made start:core an exception, so I flipped it.

---

This change is 

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch add-and-standardize-core-scripts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[imnasnainaec]

What about "core:stop": "cd ../paranext-core && npm run stop",?

(Then I can remove it from #8... where it was out-of-scope anyway.)

Also, core:start and core:stop could use npm --prefix to match core:install.