Fix yq expression syntax in configuration-converter

[MaxBab]

What type of PR is this?

• Enhancement / New Feature
• Bug Fix
• Refactor
• Optimization
• Test
• Documentation Update

What this PR does / why we need it:

The validate_spec_components function in configuration-converter.sh was failing with "Error: bad expression, please check expression syntax" on extracting "components" keys.

The original command attempted to delete non-"enabled" keys using: del(.spec.components.[] | keys[] | select(. != "enabled"))

This failed because:

• .spec.components.[] incorrectly tries to iterate over object values
• keys[] syntax doesn't work in this pipeline context in yq v4
• select(. != "enabled") references values instead of key names
• No proper context management for applying deletions back to document

Replaced with proper yq v4 syntax using the with() function.

Which issue(s) this PR fixes:

Fixes #

Related Issue/PR #

Additional information:

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.03%. Comparing base (c1aaf0e) to head (c743475).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1519      +/-   ##
==========================================
+ Coverage   80.94%   81.03%   +0.08%     
==========================================
  Files          44       44              
  Lines        2299     2299              
==========================================
+ Hits         1861     1863       +2     
+ Misses        322      321       -1     
+ Partials      116      115       -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.

[MaxBab]

/test tools-hack-check

[MaxBab]

/cherry-pick release-1.28

[istio-testing]

@MaxBab: only istio-ecosystem org members may request cherry picks. If you are already part of the org, make sure to change your membership to public. Otherwise you can still do the cherry-pick manually.

Details

In response to this:

/cherry-pick release-1.28

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[fjglira]

/cherry-pick release-1.28

[fjglira]

/cherry-pick release-1.27

[fjglira]

/cherry-pick release-1.26

[istio-testing]

@fjglira: new pull request created: #1524

Details

In response to this:

/cherry-pick release-1.28

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[istio-testing]

@fjglira: new pull request created: #1525

Details

In response to this:

/cherry-pick release-1.27

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[istio-testing]

@fjglira: new pull request created: #1526

Details

In response to this:

/cherry-pick release-1.26

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.