fix: improve request body / content-type handling (#349)

- instead of using the first `requestBody` `content-type`,
  search for the first supported one.

- when none are currently supported, output a `never` type,
  and a `todo` comment to make this clear to the user.

- subsequent changes to support for `text/plain`,
`application/x-www-form-urlencoded`, `application/octet-stream` and
`multipart/form-data` are planned to follow reasonably quickly, but they
might not become supported for every template at once, and this feels
like a fairer representation

- also start cleaning integration tests before generation

Author: mnahkies

.nvmrc

@@ -1 +1 @@
-24.1.0
+24.4.1

e2e/src/generated/client/axios/client.ts

@@ -1,5 +1,5 @@
 {
-  "name": "typescript-angular",
+  "name": "@integration/typescript-angular",
   "version": "0.0.0",
   "scripts": {
     "clean": "rm -rf ./dist && rm -rf ./src/generated",