Preparing to add fastify server impl.

Codegen is incoming!

And generate conformance plugin.

- all but three conformance tests are passing (mirrorBytes, mirrorText, and bodyTypes) which will require a bit of work to configurare the fastify server, as well as potential changes to the generated client, which assumes that fetch requests come back with JSON.

- This allows the plugin to live anywhere without needing to know where the client type file is. I debated creating a new type file instead of inlining them in the plugin, but didn't really see a point since it is just for the server to use. Perhaps I'm missing something though...

No longer needed!

- This allows the plugin to live wherever the user wants it to live.
- Ideally I would think the express server should be generated the same way
but that would be a breaking change, so maybe not needed?

As well, we are now running all conformance tests together, testing all client and server code.

https://fastify.dev/docs/latest/Reference/Validation-and-Serialization/#serialization

I opted to only handle response schemas since (from my understanding) that is where most of the performance gain is at using `fast-json-stringify`. The request schemas are mostly for validation, which Facility can already take care of for us.

instead of digging into the type name directly.

Instead we just set it to a suggestion in `.editorconfig`

Add JsonSchema support to fastify plugin.

Allows appending a custom suffix to generated file names before the extension. For example, if the suffix is `.g`, the generated client file name would be `moduleName.g.js` (or `moduleName.g.ts` when using TypeScript).

* Publish 2.10.0.

* Update release notes.

…ityApi#63)