### Motivation

This solves the missing import issue described in
#755

### Modifications

Update the version of generator in`Makefile`
Updated runtime versions to latest released version

### Result

Solved the `is not available due to missing import of defining module
'Foundation'` issue

```text
 13 | //===----------------------------------------------------------------------===//
 14 | import OpenAPIKit
 15 |
    | `- note: add import of module 'Foundation'
 16 | /// Represents a server variable and the function of generation that should be applied.
 17 | protocol ServerVariableGenerator {
    :
166 |             self.key = key
167 |             swiftSafeKey = context.safeNameGenerator.swiftMemberName(for: key)
168 |             enumName = context.safeNameGenerator.swiftTypeName(for: key.localizedCapitalized)
    |                                                                         `- error: property 'localizedCapitalized' is not available due to missing import of defining module 'Foundation'
169 |             self.variable = variable
170 |             self.enumValues = enumValues
/Volumes/w/src/github.com/apple/swift-openapi-generator/Examples/manual-generation-generator-cli-example/.swift-openapi-generator/Sources/_OpenAPIGeneratorCore/Translator/TypesTranslator/translateServersVariables.swift:168:73: error: property 'localizedCapitalized' is not available due to missing import of defining module 'Foundation'
 13 | //===----------------------------------------------------------------------===//
 14 | import OpenAPIKit
```

### Test Plan

Passed locally, `make generate` and `swift run`.

At some point recently (I only noticed it in
https://github.com/apple/swift-openapi-generator/actions/runs/17734822822/job/50426205189?pr=816)
we started getting failures in PR CI due to formatting issues in a test
and in example projects.

This PR fixes them up.

…only responses (#816)

### Motivation

Fix typos in the doc.

### Motivation

Fixes #769
Currently, as seen in the issue mentioned above, if a recursive schema
gets referenced from a multipart-based path, a reference cycle error
gets thrown. Since we support recursive type generation already, this
shouldn't happen.

### Modifications

This PR removes the last `dereferenced(in:)` method call, which would
throw if a reference cycle was found, replacing it with a simple lookup
in the OpenAPI components tree. It also replaces
`DerereferencedJSONSchema` with `JSONSchema` accordingly.

### Result

Multipart-based paths can now reference recursive types.

### Test Plan

This also adds a test with such a case. We could probably also add a
test with a multipart path referencing an _array_ of references instead
of just a reference to be thorough.