[elixir] elixir generator failing to compile + invalid references

[ariesclark]

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh
  ./bin/utils/export_docs_generators.sh
  

  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  For Windows users, please run the script in Git BASH.
• In case you are adding a new generator, run the following additional script :

  ./bin/utils/ensure-up-to-date.sh
  

  Commit all changed files.
• File the PR against the correct branch: master (6.3.0) (minor release - breaking changes with fallbacks), 7.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@mrmstn, but doubt we'd need their review to merge this.

[ariesclark]

So, apparently the generator doesn't work at all, even with these changes, annoying...
Models are returned empty, status codes are ignored, responses return things like {:ok, %VRChat.Model.Error%{}}, many models contain references that just don't exist.. [VRChat.Model.String.t()]

To see what I'm experiencing, try generating using this specification:
https://raw.githubusercontent.com/vrchatapi/specification/gh-pages/openapi.yaml

[mrmstn]

I am currently on holiday and will review this PR as soon as I return.

In the meantime, please create an issue addressing the problems you are experiencing. To help expedite the resolution process, kindly provide the following information:

• For incorrect referencing, please specify the property name that contains the erroneous reference. This will help us identify and debug any potential side effects arising from format: or other property details.
• For issue with the response code mapping, it is crucial to examine the HTTP request from the server. You can capture this by executing curl in verbose mode -v. Please replace your secrets with ***** or something similar.

Additionally, please include snippets from the generated models and API modules, as they will be valuable in understanding the issue.

Thank you for your cooperation and understanding.

[efcasado]

@mrmstn, @wing328 - This pull request can be closed, right?