oe-go-mod-fetcher: improve error messages with recipe-ready fix snippets

When the fetcher encounters unverifiable commits or modules with no
repository metadata, the error messages now show two equivalent options:

  Option 1: For bitbake users (most common) — add GO_MOD_VCS_EXCLUDE
  and a gomod:// SRC_URI entry to the recipe, fetching the module via
  the Go module proxy instead of git.

  Option 2: For direct oe-go-mod-fetcher.py invocation — pass
  --inject-commit / --set-repo on the command line with a complete
  example showing all required arguments.

Both options produce the same result. The previous messages only
suggested --inject-commit and --set-repo without context on where
or how to use them.

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>

0 files changed, 0 insertions, 0 deletions