[FEATURE]: Collapse profiler variants

[dgomez04]

Problem

Several source profilers expose a variant prompt that segregates the SQL pipeline by development type or optional feature availability instead of discovering it automatically, causing a friction-heavy user experience and duplicated pipeline logic:

• Redshift (provisioned, provisioned_multi_az, serverless)
• Teradata (core, pdcr)

We should discover this rather than exposing it.

Proposed Solution

For each affected source, collapse its variants into a single, self-describing pipeline. Move deployment/feature identification downstream to the analysis/model layer based on the extracted data artifacts, relying on the best-effort/partial-run contract from #2541 to tolerate queries that are only valid for a subset of environments.

High-Level Acceptance Criteria

• Redshift profiling runs seamlessly without requiring a variant choice or prompting the user. (Consolidate the Redshift profiler into a single pipeline and remove variant selection #2542)
• Teradata profiling runs seamlessly without requiring a core/pdcr choice or prompting the user.
• A unified pipeline per source executes across all deployment/feature permutations known for that source.
• Core pipeline engine supports graceful failures for optional, mutually exclusive or additive SQL queries (Decide how the profiler pipeline should handle partial / best-effort runs. #2541).
• Downstream analysis/total cost of ownership layer accurately infers deployment type/feature availability from extract data alone.
• SOURCE_SYSTEM_VARIANTS no longer carries entries for fully-collapsed sources.

[ysmx-github]

This is the right thing to do