codescan tests fail on go 1.18

[kevinbarbour]

Problem statement

When using go 1.18 the unit tests fail due to failing tests in codescan.

Digging into it a bit I found that it is because the order of the fields in the schemas built here are different than they were in 1.17, and the tests rely on them being in a specific order.

It looks like the CI tests are still using 1.17 for linux builds, but the windows tests fail due to this.

Environment

swagger version: master
go version: 1.18
OS: macOS