[Exporter] Skip exporting of tables and dashboards created by lakehouse monitoring

[alexott]

Collect table names and dashboard IDs from the get API:

• profile_metrics_table_name
• drift_metrics_table_name
• dashboard_id

and ignore them when generating resources

1. Think about their dependencies...
2. Think about legacy monitoring dashboards - that aren't using lakeview, and create queries, etc.

[alankritjoshi]

@alexott what's the intent behind ignoring those tables for resource generation?

Just trying to understand this because I have a related issue:

1. I use the Schema resource to create one and then reference it for creating a LakehouseMonitor
2. However, I am unable to destroy the stack due to the inclusion of the two tables. I get an error like this:

cannot delete schema: Schema 'sandbox.example' is not empty. The schema has 2 tables(s), 0 functions(s), 0 volumes(s)

[alexott]

it's for exporter - because these tables/dashboards are handled by quality monitors. Also, it's not implemented yet