Description

This PR simplifies the generated Connection module according to the discussion here. The new approach is more idiomatic and improves the maintainability of the generator.

Additionally, it resolves the issue reported in #20562 by removing the problematic function specification from the generated code. The issue can be reproduced using Stripe's OpenAPI specification, available here.

== Compilation error in file lib/connection.ex ==
** (MismatchedDelimiterError) mismatched delimiter found on lib/connection.ex:92:45:
    error: unexpected token: )
    │
  4 │ defmodule Stripe.Connection do
    │                             └ unclosed delimiter
 ...
 92 │   @spec new(String.t(), String.t()), options) :: Tesla.Env.client()
    │                                             └ mismatched closing delimiter (expected "end")
    │
    └─ lib/connection.ex:92:45
    (elixir 1.18.3) lib/kernel/parallel_compiler.ex:428: anonymous fn/5 in Kernel.ParallelCompiler.spawn_workers/8

With these changes, #15075 becomes unnecessary.

I considered targeting the 8.0.x branch, but since the Elixir generator is still in alpha and this change also fixes a known issue, I believe it makes more sense to target master directly. What do you think?

As usual, curious to hear your thoughts @mrmstn and @wing328 😊

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 || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in Git BASH)
  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*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.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.