fix: add publishConfig to package.json (#466)

<!-- 👋 Hi, thanks for sending a PR to template-typescript-node-package!
💖.
Please fill out all fields below and make sure each item is true and [x]
checked.
Otherwise, we may not be able to review your PR. -->

## PR Checklist

- [x] Addresses an existing open issue: fixes #465 
- [x] That issue was marked as [`status: accepting
prs`](https://github.com/JoshuaKGoldberg/template-typescript-node-package/issues?q=is%3Aopen+is%3Aissue+label%3A%22status%3A+accepting+prs%22)
- [x] Steps in
[CONTRIBUTING.md](https://github.com/JoshuaKGoldberg/template-typescript-node-package/blob/main/.github/CONTRIBUTING.md)
were taken

## Overview

<!-- Description of what is changed and how the code change does that.
-->
Added the following property to package.json

"publishConfig": {
	"provenance": true
  },
This will indicate for published npm packages to use [package
provenance](#465),
which is a new and important security practice.

Author: promise-dash

package.json

@@ -92,5 +92,8 @@
 	"packageManager": "[email protected]",
 	"engines": {
 		"node": ">=18"
+	},
+	"publishConfig": {
+		"provenance": true
 	}
 }