Remove redundant size hint for request info map

[kallydev]

Summary

🤖 Generated by Copilot at c6f022b

Refactor and simplify code related to HTTP CONNECT protocol. Move GetHTTPSHostname function from pkg/util/vhost/https.go to pkg/util/tcpmux/httpconnect.go and omit zero size argument for reqInfoMap variable.

WHY

golangci-lint updated gosec rules in v1.54.2. golangci/golangci-lint#4015

➜  frp git:(dev) golangci-lint run                        
pkg/util/vhost/https.go:47:2: G602: Potentially accessing slice out of bounds (gosec)
        reqInfoMap["Host"] = clientHello.ServerName
        ^
pkg/util/vhost/https.go:48:2: G602: Potentially accessing slice out of bounds (gosec)
        reqInfoMap["Scheme"] = "https"
        ^
pkg/util/tcpmux/httpconnect.go:104:2: G602: Potentially accessing slice out of bounds (gosec)
        reqInfoMap["Host"] = host
        ^
pkg/util/tcpmux/httpconnect.go:105:2: G602: Potentially accessing slice out of bounds (gosec)
        reqInfoMap["Scheme"] = "tcp"
        ^
pkg/util/tcpmux/httpconnect.go:106:2: G602: Potentially accessing slice out of bounds (gosec)
        reqInfoMap["HTTPUser"] = httpUser
        ^
pkg/util/tcpmux/httpconnect.go:107:2: G602: Potentially accessing slice out of bounds (gosec)
        reqInfoMap["HTTPPwd"] = httpPwd
        ^

[fatedier]

We use a specified golangci-lint version https://github.com/fatedier/frp/blob/dev/.golangci.yml#L2C1-L2C1 .

We don't always update all dependencies to the latest version, we do so at the appropriate time.

Finally, what you modified is map, not slice. That looks like a false alarm. This is also why we don't always update our dependency tools to the latest version.

[kallydev]

It has been verified that this is not an issue with the frp main repository, it is caused by a downstream fork that changed the golangci-lint version to 1.54. The gosec rule change was introduced when the CI automatically upgraded from 1.54.1 to 1.54.2 due to not locking the patch version number (x.y.Z) of golangci-lint in the CI configuration file.

I will close this PR because the issue doesn't actually exist, and it's a false positive warning.

Thanks for your review!