Fix missing signature key error when pulling Docker images with SERVE_DIRECT enabled

[Zettat123]

Fix #28121

I did some tests and found that the missing signature key error is caused by an incorrect Content-Type header. Gitea correctly sets the Content-Type header when serving files.

gitea/routers/api/packages/container/container.go

Lines 712 to 717 in 348d1d0

	headers := &containerHeaders{
	ContentDigest: pfd.Properties.GetByName(container_module.PropertyDigest),
	ContentType: pfd.Properties.GetByName(container_module.PropertyMediaType),
	ContentLength: pfd.Blob.Size,
	Status: http.StatusOK,
	}

However, when SERVE_DIRECT is enabled, the Content-Type header may be set to an incorrect value by the storage service. To fix this issue, we can use query parameters to override response header values.

https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html

In this PR, I introduced a new parameter to the URL method to support additional parameters.

URL(path, name string, reqParams url.Values) (*url.URL, error)

---

Most S3-like services support specifying the content type when storing objects. However, Gitea always use application/octet-stream. Therefore, I believe we also need to improve the Save method to support storing objects with the correct content type.

gitea/modules/storage/minio.go

Lines 214 to 221 in b7fb20e

	minio.PutObjectOptions{
	ContentType: "application/octet-stream",
	// some storages like:
	// * https://developers.cloudflare.com/r2/api/s3/api/
	// * https://www.backblaze.com/b2/docs/s3_compatible_api.html
	// do not support "x-amz-checksum-algorithm" header, so use legacy MD5 checksum
	SendContentMd5: m.cfg.ChecksumAlgorithm == "md5",
	},

[Zettat123]

I'm not sure if other package managers also have content type issues, so I didn't specify a content type for them.

[GiteaBot]

I was unable to create a backport for 1.22. @Zettat123, please send one manually. 🍵

go run ./contrib/backport 32365
...  // fix git conflicts if any
go run ./contrib/backport --continue