revert swagger-parser upgrade

[ctreatma]

This addresses #17554 by downgrading swagger-parser to the version that was used in the 7.1.0 release of openapi-generator.

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

  (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.1.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.

[ctreatma]

@wing328 I think it would be good to get a test in place using the sample schema @ttrubinov shared in swagger-api/swagger-parser#2037 so that we can proactively catch this when the parser is upgraded in the future. What's the best place to put a test like that? I've only added language-specific tests so far, but this isn't a language-specific issue.

[wing328]

shall we try upgrading to 2.1.20 which was released 4 days ago to see if the issue persists?

[ctreatma]

shall we try upgrading to 2.1.20 which was released 4 days ago to see if the issue persists?

As I understand it, the swagger-parser folks didn't start looking into this bug until after 2.1.20 was cut; setting that aside, though, it would still be helpful to have tests somewhere in this repo to protect against this bug, and those tests would tell us if 2.1.20 or a later version of swagger parser has fixed the issue. Is there a good place to put a test that isn't really specific to a particular language? Or is the best approach to just add a test for this bug in the go client generator tests?

[wing328]

Ok. make senses.

Or is the best approach to just add a test for this bug in the go client generator tests?

please add a test in the go client generator: modules/openapi-generator/src/test/java/org/openapitools/codegen/go/GoClientCodegenTest.java

please also merge the latest master into your branch as i've fixed the docker test failure in the latest master

[wing328]

PR merged. please add a test later when you've time. thank you 🙏