Add CLI command `dab auto-config-simulate`

[RubenCerna2079]

New CLI commands need to be added in order to allow the users to change the autoentities properties inside of the config file.
Introduce a new autoentities configure subcommand that operates like an upsert.
These commands need to follow the existing coding pattern that we have for the other CLI commands

dab auto-config-simulate --output file.json

This command will output all of the existing entities that are created from the autoentities configuration

• The output flag is optional, if it doesn’t appear then it will be output into the console
• The things that will be outputed for each entity is the alias, definition-name, and object name
• File output is csv

[JerryNixon]

The purpose of dab autoentities simulate is to allow developers to see the result of their filters against the database.

Output to the console:

dab autoentities simulate

Output format

AutoEntities Simulation Results

Filter: <filter_name>
Matches: <count>

<entity_name> -> <schema_name>.<object_name>
<entity_name> -> <schema_name>.<object_name>

• Output is grouped by filter.
• If a filter has zero matches, output:

(no matches)

Output example

AutoEntities Simulation Results

Filter: ProductTables
Matches: 3

Products  -> dbo.Products
Inventory -> dbo.Inventory
Pricing   -> dbo.Pricing

Filter: AnotherFilter
Matches: 0

(no matches)

Output to a file:

dab autoentities simulate --output file.txt

• If file name is invalid throw an exception
• If file already exists overwrite it (no prompt)

Output format (CSV)

• CSV includes a header row.
• Each match is output as one CSV line.

filter_name,entity_name,database_object

Where database_object is <schema_name>.<object_name>.

Output example (CSV)

filter_name,entity_name,database_object
ProductTables,Products,dbo.Products
ProductTables,Inventory,dbo.Inventory
ProductTables,Pricing,dbo.Pricing