fix: correct inverted guard in WithRegistryIDs/WithProtocolIDs

[MaoMengww]

Description

Fixes # (issue)
The root cause of the bug is an inverted guard condition. When a user use RegistryIDs/ProtocolIDs, a non-empty value should be written to the field; however, due to the inverted guard condition, the assignment is skipped whenever the user provides a value (i.e., len(IDs) > 0), causing it to be silently dropped. The test file： when a non-empty value is passed, the assertion should be that the field equals the input (assert.Equal), not that it differs (assert.NotEqual).

Refs #3598 (task1)

Checklist

• I confirm the target branch is develop
• Code has passed local testing
• I have added tests that prove my fix is effective or that my feature works

[MaoMengww]

@Alanxtl please review it

[sonarqubecloud]

Quality Gate passed

Issues
0 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

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 53.87%. Comparing base (60d1c2a) to head (5c7c5b0).
⚠️ Report is 891 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3604      +/-   ##
===========================================
+ Coverage    46.76%   53.87%   +7.10%     
===========================================
  Files          295      474     +179     
  Lines        17172    36388   +19216     
===========================================
+ Hits          8031    19604   +11573     
- Misses        8287    15208    +6921     
- Partials       854     1576     +722     

☔ View full report in Codecov by Harness.
📢 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.

[Alanxtl]

lgtm