feat: add wildcard support for ingress class matching

[czuares]

Summary

This PR adds wildcard pattern support for ingress class matching in the --alb-ingress-classes and --nginx-ingress-classes flags.

Motivation

When managing multiple ingress controllers with similar naming patterns (e.g., nginx-internal, nginx-external, nginx-staging), users currently need to specify each class individually. This becomes cumbersome and error-prone when the number of ingress classes grows.

Changes

Core Implementation

• Updated hasClass() function in ingress/ingress.go to support wildcard patterns:
  • * - matches any ingress class
  • prefix-* - matches classes starting with the prefix
  • *-suffix - matches classes ending with the suffix

Testing

• Added comprehensive unit tests in ingress/ingress_test.go with 24 test cases covering:
  • Exact matching (existing behavior)
  • Wildcard matching (*)
  • Prefix wildcards (prefix-*)
  • Suffix wildcards (*-suffix)
  • Mixed patterns
  • Edge cases

Documentation

• Updated docs/features/traffic-management/nginx.md with wildcard pattern documentation and examples
• Updated docs/features/traffic-management/alb.md with wildcard pattern documentation and examples

Examples

# Match all nginx-* classes
--nginx-ingress-classes nginx-*

# Match multiple patterns
--nginx-ingress-classes nginx-* --nginx-ingress-classes custom-nginx

# Match all ingress classes
--nginx-ingress-classes '*'

Checklist

• Code changes implemented
• Unit tests added and passing
• Documentation updated
• Backward compatible (exact matching still works)

Testing

All existing tests pass, and new tests verify the wildcard functionality:

go test -v ./ingress -run TestHasClass

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Published E2E Test Results

  4 files    4 suites   3h 30m 45s ⏱️
120 tests 111 ✅  7 💤 2 ❌
482 runs  452 ✅ 28 💤 2 ❌

For more details on these failures, see this check.

Results for commit faeea3a.

[github-actions]

Published Unit Test Results

2 416 tests   2 416 ✅  3m 4s ⏱️
  129 suites      0 💤
    1 files        0 ❌

Results for commit faeea3a.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.41%. Comparing base (348260a) to head (faeea3a).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4615      +/-   ##
==========================================
+ Coverage   84.40%   84.41%   +0.01%     
==========================================
  Files         164      164              
  Lines       18855    18865      +10     
==========================================
+ Hits        15914    15925      +11     
  Misses       2077     2077              
+ Partials      864      863       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.