Add description to docs for proximity views

[Damonamajor]

Quick fix to add columns to the yaml file to produce the docs for missing proximity views.

[jeancochrane]

A few small changes to make sure this is all buttoned up!

[jeancochrane]

[Suggestion, optional] As long as we're cleaning up these docs, I figure we might as well remove this column definition, since it doesn't seem to be part of either vw_pin10_proximity or vw_pin10_proximity_fill anymore.

[jeancochrane]

[Nitpick, required] It looks like these fields are defined in the vw_pin10_proximity_fill query:

data-architecture/dbt/models/proximity/proximity.vw_pin10_proximity_fill.sql

Lines 20 to 25 in 76a64f9

	dist_pin_to_airport.airport_ohare_dist_ft,
	dist_pin_to_airport.airport_midway_dist_ft,
	dist_pin_to_airport.airport_dnl_total,
	dist_pin_to_airport.airport_data_year,

But they're not defined in vw_pin10_proximity:

data-architecture/dbt/models/proximity/proximity.vw_pin10_proximity.sql

Lines 20 to 22 in 76a64f9

	dist_pin_to_airport.airport_dnl_total,

That means they end up with blank types in the vw_pin10_proximity docs, since those fields are not present in the table, meaning dbt can't infer types for them:

Maybe @wrridgeway knows why these airport metadata fields are missing from vw_pin10_proximity? If there's no good reason for the discrepancy, then the easiest fix here should just be to add these metadata fields to the vw_pin10_proximity query, which will automatically populate their data types in the dbt docs.

[jeancochrane]

[Nitpick, required] Similar to above, this field is defined in vw_pin10_proximity:

data-architecture/dbt/models/proximity/proximity.vw_pin10_proximity.sql

Line 111 in 76a64f9

dist_pin_to_road_highway.nearest_road_highway_data_year,

But it's missing from vw_pin10_proximity_fill:

data-architecture/dbt/models/proximity/proximity.vw_pin10_proximity_fill.sql

Lines 107 to 114 in 76a64f9

	dist_pin_to_road_highway.nearest_road_highway_name,
	dist_pin_to_road_highway.nearest_road_highway_dist_ft,
	dist_pin_to_road_highway.nearest_road_highway_daily_traffic,
	dist_pin_to_road_highway.nearest_road_highway_speed_limit,
	dist_pin_to_road_highway.nearest_road_highway_surface_type,
	dist_pin_to_road_highway.nearest_road_highway_lanes,

Which leads to an empty data type in the docs:

@wrridgeway Same as above: Are we good to add this data_year column to vw_pin10_proximity so that it matches vw_pin10_proximity_fill?

[jeancochrane]

[Nitpick, required] These two duplicate rows, plus the absence of a description for nearest_grocery_store_data_year in the docs for both proximity.vw_pin10_proximity* tables, make me wonder if perhaps the second entry here is a typo, and we meant to document data_year?