docker: align image tags with GoReleaser artifacts

[aofei]

Following the changes introduced in #1838, this commit updates Docker image and manifest tags to align with the GoReleaser artifact naming conventions. The changes are as follows:

• Image tags have been updated from "v1.2.3-i386" to "1.2.3-386", from "v1.2.3-x86_64" to "1.2.3-amd64", "v1.2.3-arm64" to "1.2.3-arm64".
• The version prefix "v" has been removed from the image manifest tags, changing "v1.2.3" to "1.2.3", "v1.2" to "1.2", and "v1" to "1".

---

Should we keep the v prefix? I referred to the tag style of docker.io/library/golang and removed the v prefix. (See: https://hub.docker.com/_/golang/tags?name=-alpine3.19)

/cc @xushiwei @cpunion

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.63%. Comparing base (e1b4f80) to head (8faa4ae).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1841   +/-   ##
=======================================
  Coverage   92.63%   92.63%           
=======================================
  Files          41       41           
  Lines       11456    11456           
=======================================
  Hits        10612    10612           
  Misses        682      682           
  Partials      162      162           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cpunion]

The 'v' prefix should perhaps be removed anywhere, includes instances such as:

1. Version display in terminal commands:

$ go version
go version go1.22.1 darwin/arm64
$ gop version
gop v1.2.3 darwin/arm64

2. Version tags on GitHub:

• For Go:
  go1.22.2

• For Gop:
  v1.2.5

[xushiwei]

The 'v' prefix should perhaps be removed anywhere, includes instances such as:

1. Version display in terminal commands:

$ go version
go version go1.22.1 darwin/arm64
$ gop version
gop v1.2.3 darwin/arm64

2. Version tags on GitHub:

• For Go:
  go1.22.2
• For Gop:
  v1.2.5

I don’t think there’s a right answer to this question, but it’s important not to break previously established conventions.

[xushiwei]

The behavior of gop version and tag has been fixed and will not change. However, the name of the release file has not been finalized. We can determine a standard. For example, Go looks like this:

• go1.22.2.linux-386

[aofei]

The 'v' prefix should perhaps be removed anywhere, includes instances such as:

1. Version display in terminal commands:

$ go version
go version go1.22.1 darwin/arm64
$ gop version
gop v1.2.3 darwin/arm64

2. Version tags on GitHub:

• For Go:
  go1.22.2
• For Gop:
  v1.2.5

Gop, being a Go project (aka a Go module), requires v prefixed Git tags as per Go module standards. Thus, we must use the format v1.2.5.

[cpunion]

Gop, being a Go project (aka a Go module), requires v prefixed Git tags as per Go module standards. Thus, we must use the format v1.2.5.

Forgot that.

This PR is acceptable. For tagging Docker images, using the version number followed by a suffix without v prefix is more commonly.