Issue not created when go.mod is invalid

[mloiseleur]

Description

When creating a plugin, the go.mod should be valid.

For instance, when tagging with v2 and not updating go.mod path, it will fail (example on this plugin).

Errors like this can be seen on plugin-service:

{
  "level": "error",
  "plugin_name": "github.com/hhftechnology/tailscale-access",
  "plugin_version": "v2.0.0",
  "error": "error: 404: 404 Not Found: not found: github.com/hhftechnology/tailscale-access@v2.0.0: invalid version: module contains a go.mod file, so module path must match major version (\"github.com/hhftechnology/tailscale-access/v2\")",
  "caller": "/home/semaphore/go/src/github.com/traefik/plugin-service/pkg/handlers/module.go:114",
  "message": "Failed to get module file"
}

Considered options during first analysis

• Improve alerting or dashboard on 500 errors on plugin-service
• Improve error message on plugin-service when failing with 500 for this case
• During indexation, check go.mod file