Remove dependency scan for inputSpec (actually not required)

[parenko]

This PR fixes #19073.
The dependency scan introduced with #18576 is actually not required. (And I am i am sorry for the inconvenience.)
Resolution for inputSpec works with correct classpath setup or absolute file reference.
Also it is still possible to provide an JAR inputSpec. (Swagger only supports collapsed OpenApiSpec without external refs currently).

To reproduce #19073 we need a dependency which contains an OpenApiSpec with external refs and which are not in current class path. First commit in this PR does this.

CC @wing328

• 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.6.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.

[wing328]

thanks for the fix