[FEATURE] Add CPA geography column to `[inputs].[mgra]`

[Eric-Liu-SANDAG]

Is your feature request related to a problem? Please describe

We want to keep everything related to the Estimates Program within the Estimates database, which means that we can't be pulling data from [demographic_warehouse]. For reporting purposes, we should add on a CPA column to [inputs].[mgra] as it's a very common reporting geography. Other than that there's not much more we need to add, as we already have cities and tracts

Describe the solution you'd like

Add on a CPA column to [inputs].[mgra]

Describe alternatives you've considered

I almost think we should de-normalize the table as well, as that would give us the future flexibility to add in any xref we wanted to, without having to add a new column

Additional context

N/A

[GregorSchroeder]

@Eric-Liu-SANDAG are we ok with using a combination of City CPAs, County CPAs, and Jurisdiction that we have loaded into [GeoAnalyst] or do we only want the CPAs and NULLs for MGRAs that are not within the City or Unincorporated?