Give user ability to set ingestion Filter Patterns based off of tags

[traitortots]

Is your feature request related to a problem? Please describe.
When setting up or fine-tuning an ingestion, sometimes there is not a simple regex pattern that can describe what I want to include or exclude when running an ingestion on a service, so I end up typing in a ton of table names manually.

Describe the solution you'd like
It would be great to be able to use tags to identify and set filter patterns for databases, schemas, or tables during ingestion. For example, if I only want to run Profiler Ingestion on everything tagged as Tier 1, or have a tag called "Profiler-Include" that is then an input parameter for the ingestion. This would also make it easier for users without access to the ingestion setup to still contribute to deciding what is and is not ingested, and will make ingestions more dynamic as certain qualities of the data change (ie, a table is no longer considered Tier 1 and when reclassified, the ingestion manifest does not need to be edited and the table is no longer profiled).

Describe alternatives you've considered
Users continue to manually set up Include or Exclude patterns at a more granular level when regex patterns are not able to capture the needs of the user.

Additional context
N/A