Use .json instead of .exe-plugin for process plugins

Author: dsherret

README.md

@@ -33,7 +33,7 @@ await builder.addPlatform({
 });
 
 // write it to a file
-await builder.writeToPath("plugin.exe-plugin");
+await builder.writeToPath("plugin.json");
 ```
 
 1. Build each plugin for each platform.
@@ -42,4 +42,4 @@ await builder.writeToPath("plugin.exe-plugin");
    ```shell
    deno run --allow-read=. --allow-write=. create_process_plugin.ts
    ```
-4. Upload the plugin.exe-plugin file and all the zip files to the GitHub release.
+4. Upload the `plugin.json` file and all the zip files to the GitHub release.

process_plugin.ts

@@ -1,4 +1,3 @@
-import { extractCargoVersion } from "./cargo.ts";
 import { getChecksum } from "./hash.ts";
 
 export type Platform = "windows-x86_64" | "linux-x86_64" | "darwin-x86_64" | "darwin-aarch64";
@@ -39,6 +38,7 @@ export interface PluginFileBuilderOptions {
 export class PluginFileBuilder {
   #output: any = {
     schemaVersion: 2,
+    kind: "process",
   };
 
   constructor(options: PluginFileBuilderOptions) {
@@ -110,7 +110,7 @@ export async function createDprintOrgProcessPlugin({ pluginName, version, platfo
     }
   }
 
-  await builder.writeToPath("plugin.exe-plugin");
+  await builder.writeToPath("plugin.json");
 
   async function addPlatform(platform: Platform) {
     const zipFileName = getStandardZipFileName(builder.pluginName, platform);