[BUG] Noticed weird bug in v7.0.2/3 regarding extractor artifacts

### Release version

7.0.2/3

### Describe the bug

In previous versions when we run the extractor with below config, extractor will only pick up the subscription(s) details assigned to the product name given in config.

Find the example extractor config used below. (before v7.0.1)

`diagnosticNames: [ignore]
loggerNames: [ignore]
policyFragmentNames: [ignore]

apiNames:
- apiName1

backendNames:
- backendName1
- backendName2

namedValueNames:
- namedValueName1
- namedValueName2

productNames:
- productName1
- productName2

tagNames:
- tagName1
- tagName2
`
But in new version of extractor config if we do the same with new naming, extractor picking up every subscription(s) in the APIM instance with the product mention in the config.

This is causing issue for the publisher. if we run the publisher on the same, it will update all the subscription on new instance.

### Expected behavior

When we have given product in extractor config, it should only pickup related subscription. Also along with this if we have given specific API in the extractor config the api should the only api in the artifacts.

### Actual behavior

In this version, extractor pull all the APIs and Subscription attached with the product instead of the related ones like in previous versions.

### Reproduction Steps

1. Update the Version to 7.0.2
2. create the configuration.extractor.yaml with the specific api and Product( Make sure mutiple api attached to the product to see the difference) (>=v7.0.1 )

`diagnostics: []
loggers: []
policyFragments: []
gateways: []
groups: []
versionSets: []
workspaces: []

apis:
- apiName1

backends:
- backendName1
- backendName2

namedValues:
- namedValueName1
- namedValueName2

products:
- productName1
- productName2

tags:
- tagName1
- tagName2`

4. Run the extractor and observe the artifacts.

You will see, all the subscriptions attached and all the APIs are attached in the product.