Check only extensions for SCC activations

[jesusbv]

Description

When checking the registry access if system is hybrid, the check with SCC for the state of its activations should be done only with non free extensions, as base product is not free

This Fixes that scenario

How to test

on a PYG 15.4 system, register LTSS and run podman search
the result should include base product + LTSS

ip-10-3-0-101:/home/ec2-user # podman search registry-ec2.susecloud.net/
NAME                                                               DESCRIPTION
registry-ec2.susecloud.net/suse/hpc/warewulf4-x86_64/sle-hpc-node  
registry-ec2.susecloud.net/suse/ltss/sle15.4/bci-base              
registry-ec2.susecloud.net/suse/ltss/sle15.4/bci-base-fips         
registry-ec2.susecloud.net/suse/ltss/sle15.4/sle15                 
ip-10-3-0-101:/home/ec2-user # 

Change Type

Please select the correct option.

• Bug Fix (a non-breaking change which fixes an issue)
• New Feature (a non-breaking change which adds new functionality)
• Documentation Update (a change which only updates documentation)

Checklist

Please check off each item if the requirement is met.

• I have reviewed my own code and believe that it's ready for an external review.
• I have provided comments for any hard-to-understand code.
• I have documented the MANUAL.md file with any changes to the user experience.
• If my changes are non-trivial, I have added a changelog entry to notify users at package/obs/rmt-server.changes.

Review

Please check out our review guidelines
and get in touch with the author to get a shared understanding of the change.

[bear454]

Add this to technical debt; we need to refactor to a query result, instead of querying a larger set and iterating over it.

[felixsch]

lgtm 👍

How I reviewed this merge request:

• Checked the code changes are fine and suggested (or not) changes I would do
• Checked that LTSS is really a extension in SCC

As always, if you think I missed something I should test, please let me know🚀

cheers,