[go-server] fix imports with go generation

[darkrift]

This fixes the import issues raised in issue 5153

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.

[darkrift]

@antihax @grokify @kemokemo @jirikuncar @ph4r5h4d @lwj5

[wing328]

thanks for the PR. does this fix work for APIs with different tags (e.g. Pet, User) ? looks like if Pet APIs have an endpoint with body parameter while Users APIs doesn't have any body parameter, hasBodyParams is also set to true for Users APIs (operations).

[darkrift]

I actually added an open api spec and a sample generated code that creates 3 different api files with their own tags (api_none.go, api_body.go, api_path.go) to test 3 different cases, I haven't make a case for "both" but the logic is independent for both case and just a combination of body and path tag.

Each of them has the imports according to what they need to use.

[wing328]

That's good. I'll do some tests later to confirm

[wing328]

please add the output folder to .github/workflows/samples-go.yaml so that the CI can test the output moving forward

[darkrift]

Done

[wing328]

thanks for the fix.

let's give it a try