build: Ensure constant format strings in fmt and printf calls

[mikelolasagasti]

Go 1.24 introduces stricter checks for format string validation. This commit fixes instances where non-constant format strings were used in calls to functions like fmt.Errorf, fmt.Printf, and similar.

$ go version
go version go1.24rc2 linux/amd64

$ go vet -printf ./...
(...)
pkg/iac/scanners/terraform/parser/funcs/collection.go:512:48: non-constant format string in call to github.com/zclconf/go-cty/cty/function.NewArgErrorf
pkg/iac/scanners/terraform/parser/funcs/crypto.go:178:64: non-constant format string in call to github.com/zclconf/go-cty/cty/function.NewArgErrorf

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[mikelolasagasti]

Not sure what's going on with CLAassistant, but as first comment says it's signed ¯\(ツ)/¯