[go] Path of the remote file added to the pattern when generating a server

Description

When using option -i to grab the specs from the web to generate a server, the path of the specs is added to the Route pattern

The command used is

swagger-codegen generate -i  https://forge.3gpp.org/rep/all/5G_APIs/-/blob/Rel17-draft-TSG96/TS29122_PfdManagement.yaml  -l go-server -o server

The result at routers.go is

var routes = Routes{
	Route{
		"Index",
		"GET",
		"/rep/all/5G_APIs/-/raw/Rel17-draft-TSG96//TS29122_PfdManagement.yaml/",
		Index,
	},

	Route{
		"DeleteIndApplicationPFDManagement",
		strings.ToUpper("Delete"),
		"/rep/all/5G_APIs/-/raw/Rel17-draft-TSG96//TS29122_PfdManagement.yaml/{scsAsId}/transactions/{transactionId}/applications/{appId}",
		DeleteIndApplicationPFDManagement,
	},
...

As you can see the 3rd argument on the Route (pattern) includes the path of the file we used

Swagger-codegen version

3.0.34

Swagger declaration file content or url

https://forge.3gpp.org/rep/all/5G_APIs/-/blob/Rel17-draft-TSG96/TS29122_PfdManagement.yaml

Command line used for generation

swagger-codegen generate -i  https://forge.3gpp.org/rep/all/5G_APIs/-/blob/Rel17-draft-TSG96/TS29122_PfdManagement.yaml  -l go-server -o server

Steps to reproduce

check routers.go

Related issues/PRs

Suggest a fix/enhancement

Reproduce the issue with the provided swagger-codegen command and inspect the generated routers.go. Compare the route patterns with the paths in the remote OpenAPI specification; done means the generated patterns contain the API routes without the remote file path prefix.