multi: update mapstructure/v2

[starius]

Change Description

go-viper's mapstructure is being updated to the version where the bug is fixed.

Steps to Test

make unit

Pull Request Checklist

Testing

• Your PR passes all CI checks.
• Tests covering the positive and negative (error paths) are included.
• Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

• The change is not insubstantial. Typo fixes are not accepted to fight bot spam.
• The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
• Commits follow the Ideal Git Commit Structure.
• Any new logging statements use an appropriate subsystem and logging level.
• Any new lncli commands have appropriate tags in the comments for the rpc in the proto file.
• There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our Contribution Guidelines for further guidance.

[ziggie1984]

related to https://github.com/lightningnetwork/lnd/security/dependabot/165

[ziggie1984]

@gemini-code-assist updating the libaries is one step, but for LND to use the updated libs we need to use the updated modules there as well, otherwise we are not using the updated lib in LND

[gemini-code-assist]

That's a very good point, @ziggie1984. You're right that simply updating the go.mod entries is only the first step.

This pull request updates the mapstructure/v2 dependency to v2.4.0 across all go.mod files within the repository (root, kvdb, sqldb, and tools). When go mod tidy and subsequent go build commands are executed, the Go module system should correctly resolve to use v2.4.0 for any module that directly or transitively depends on mapstructure/v2.

The intention is that by updating all go.mod files, the entire LND project will indeed use the updated library. The make unit command, as specified in the PR description, should help verify that the updated libraries are correctly integrated and that no unexpected issues arise from this version bump.

[ziggie1984]

Makes sense, LND will use the newest version of the map lib because of the Minimal Version Selection principal of the go tool management