Scenario parameter does not work as expected

[pauldewaal-disy]

Describe the bug
In case I use cmd line parameter "scenario", I would expect that any other JSON file in my namespace, that is not included in the scenario-list, is ignored during generation.

To Reproduce
Steps to reproduce the behavior:

1. Schema (if applicable)
   I have generated a couple of collections in a new namespace, using the import integration with Postgres.
   The dimensional tables in my Postgres schema already contain valid data. For this particular use case, I want to generate data exclusively for my transactional tables, not the dimensional table. Therefore, I applied the scenario parameter during generation, and I included only the collections in my scenario-list that should be considered for generating data.

2. See error
According to the error, synth is still looking into some collections that I meant to exclude from data generation.

![image](https://user-images.githubusercontent.com/122522371/212026923-260e7526-f194-4336-855f-86e787288f41.png)


**Expected behavior**
When I apply the scenario parameter at generation time, I would expect that any other JSON file in my namespace, that is not included in the scenario-list, is ignored during generation.

**Screenshots**
Please see screenshot above

**Environment (please complete the following information):**
 - Mac OS Monterey 12.3 (M1 architecture)

**Additional context**
Add any other context about the problem here.