Add NIPA and program-admin nonfiler controls to the US target profile

[MaxGhenis]

Problem

The US target profile needs independent/non-CPS target families for poverty resources and nonfilers. SOI covers filer/tax-form controls, but poverty and transfer-resource calibration also needs full-population and program-admin controls.

Scope

Add or verify Populace target loading/mapping for source-backed hard-target families enumerated in the Arch US poverty/nonfiler coverage contract:

• BEA NIPA: wages/salaries, personal income components, personal income disposition, pension contributions.
• IRS SOI filer/tax-form controls where applicable.
• SSA Social Security and SSI.
• USDA SNAP.
• HHS ACF TANF and LIHEAP.
• CMS health program controls: Medicaid/CHIP, ACA, Medicare Part B premium income, NHE totals.
• Census controls: PEP population age/sex, ACS age demographics where used, state individual income tax collections.

Do not activate CPS SPM, DINA, or ACS poverty/income distributions as hard targets for this fix. Those belong in validation diagnostics.

Acceptance criteria

• The US target profile has a structured inventory showing each hard-target family as active, mapped-but-inactive, or reviewed-excluded.
• NIPA full-population controls are included for non-SOI income/transfer/tax backstops.
• Program-admin SNAP/SSI/TANF/LIHEAP/CMS controls are represented as source-backed targets or explicitly excluded with reasons.
• Release diagnostics report target fit by source family.
• Tests prevent validation-only families from being activated as hard targets.

[MaxGhenis]

PE-US-data backlog migration note from #46: this issue should absorb the still-relevant program-admin/takeup targets from policyengine-us-data, specifically PolicyEngine/policyengine-us-data#1148 / PR #1162 for CHIP, #1147, #620 / PR #1087, #889, #510 for ACA/APTC, #1136 and #557 for Medicaid, and #1094, #188, #189, #122, #1021 for SSI/OASDI/disability support. These should be implemented as Populace source/target specs plus shared runtime behavior, not by porting old pipeline code.