Update hcl and go-cty dependencies

[alisdair]

Update hcl to v2.7.0 and go-cty to latest commit. These changes support the sensitive variable work in 0.14.

Fixes #25326

hcl v2.7.0 changelog

Enhancements

• json: There is a new function ParseWithStartPos, which allows overriding the starting position for parsing in case the given JSON bytes are a fragment of a larger document, such as might happen when decoding with encoding/json into a json.RawMessage. (#389)
• json: There is a new function ParseExpression, which allows parsing a JSON string directly in expression mode, whereas previously it was only possible to parse a JSON string in body mode. (#381)
• hclwrite: Block type now supports SetType and SetLabels, allowing surgical changes to the type and labels of an existing block without having to reconstruct the entire block. (#340)

Bugs Fixed

• hclsyntax: Fix confusing error message for bitwise OR operator (#380)
• hclsyntax: Several bug fixes for using HCL with values containing cty "marks" (#404, #406, #407)

go-cty changelog

• function: Unless a parameter has AllowMarks: true explicitly set, the functions infrastructure will now guarantee that it never sees a marked value even if the mark is deep inside a data structure. Previously that guarantee was only shallow for the top-level value, similar to AllowUnknown, but because marks are a relatively new addition to cty and numerous existing functions are not written to deal with them this is the more conservative and robust default. (#72)
• function/stdlib: The formatdate function was not correctly handling literal sequences at the end of the format string. It will now handle those as intended. (#69)

[codecov]

Codecov Report

Merging #26585 into master will decrease coverage by 0.00%.
The diff coverage is n/a.

Impacted Files	Coverage Δ
terraform/evaluate.go	49.66% <0.00%> (-0.45%)	⬇️
dag/walk.go	92.30% <0.00%> (+0.69%)	⬆️

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.