build: upgrade anchore dependencies to fix mapstructure compatibility

[leodido]

Description

Upgrades anchore dependencies to resolve a critical compatibility issue between different mapstructure package versions that was preventing the cmd package tests from running.

Root Cause:

• Older anchore/fangs (v0.0.0-20241014225144-4e1713cafd77) used mitchellh/[email protected]
• Newer viper (v1.20.1) uses go-viper/mapstructure/[email protected]
• Function signature mismatch in DecoderConfigOption caused build failures

Solution:

• Upgrade anchore/clio to v0.0.0-20250926015255-f418e0b4892c
• This brings anchore/fangs to v0.0.0-20250924221602-895877cb39ec
• Newer fangs is compatible with the newer mapstructure API

Key Changes:

• Primary: github.com/anchore/clio upgraded
• Secondary: github.com/anchore/fangs upgraded (transitive)
• Additional: Various dependency updates (fsnotify, gookit/color, cobra, etc.)

Related Issue(s)

Fixes cmd package test execution failures with error cannot use func(dc *mapstructure.DecoderConfig) as viper.DecoderConfigOption.

Prerequisite to have tests running in #247.
Hence, it also fixes https://linear.app/ona-team/issue/CLC-1958/leeway-security-testing-suite

How to test

Verify Tests Pass

# These should now work (previously failed)
go test ./cmd/ -v
go test -run TestBuildCommandFlags ./cmd/
go test -run TestInFlightChecksumsEnvironmentVariable ./cmd/

###Verify Binary Builds

# This should work without errors
go build -o leeway .
./leeway --help

Verify No Regression

# Existing functionality should be unchanged
go test ./pkg/... -v

Documentation

This is a dependency upgrade that fixes build/test issues without changing user-facing functionality.