References in nested schema do not match naming strategy

### Description

When creating schema definitions with `ToOpenApiSchemas` the "$ref" paths do not use the provided `CamelCaseNamingStrategy`.

Expected:
```yaml
definitions:
foo:
type: object
properties:
bar:
$ref: '#/definitions/bar'
bar:
type: object
properties:
data:
type: string
```

Actual:
```yaml
definitions:
foo:
type: object
properties:
bar:
$ref: '#/definitions/Bar'
bar:
type: object
properties:
data:
type: string
```

This causes issues when validating the swagger document.

### Steps to reproduce

Sample project to come

No source file or test is named; start from the ToOpenApiSchemas call described in the issue and reproduce the nested schema output with CamelCaseNamingStrategy. Compare the generated $ref paths with the definition names, then verify that the resulting Swagger document validates and matches the expected YAML.

Written by the indexing model from the issue text.