[BUG] Forward slash in model keyword generates invalid Elixir code

Bug Report Checklist

• Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator (example)?
• Have you tested with the latest master to confirm the issue still exists?
• Have you searched for related issues/PRs?
• What's the actual output vs expected output?
• [Optional] Sponsorship to speed up the bug fix or feature request (example)

Description

Generating an Elixir client with a spec containing a model with a "/" character in a keyword produces Elixir code which does not compile.

The issue occurs in the generated struct definition, which ends up like this:

@derive Jason.Encoder
defstruct [
  :"height/round/step",
  :start_time,
 <snipped>
]

This produces a compile error:

** (Jason.EncodeError) invalid byte 0x2F in literal key: "height/round/step"

The error occurs because while the "/" is valid in an atom name when wrapped in quotes, it is not valid as a struct field name.

openapi-generator version

7.3.0

OpenAPI declaration file content or url

https://docs.cometbft.com/v0.38/rpc/openapi.yaml

Generation Details

Default settings

Steps to reproduce

openapi-generator-cli generate -i https://docs.cometbft.com/v0.38/rpc/openapi.yaml -g elixir -o ./openapi
cd openapi
mix do deps.get, compile

Related issues/PRs

Suggest a fix

Some kind of mapping may need to be generated for keywords that include characters not valid in struct fields.

Reproduce the issue with the provided OpenAPI declaration and the openapi-generator-cli Elixir generation commands, then inspect the generated struct definition containing the slash-bearing keyword. Identify the Elixir generator path responsible for struct fields and verify completion by running mix do deps.get, compile without the invalid-byte error.