Commit changed pipeline files from rebuilding GCM driver nc files

[hcorson-dosch-usgs]

Following the addition of the wind transform code #354, I rebuilt the GCM nc files on Tallgrass.

This PR commits the changed files associated with that rebuild:

• '7_drivers_munge.yml' - build date for targets sub-pipeline
• '7_drivers_munge/out/7_GCM_driver_files.ind' - Indictor file reflecting changes to the '7_drivers/munge/out/GCM_{}.nc' files resulting from #354 and changes to '7_drivers_munge/out/lake_cell_tile_xwalk.csv' and '7_drivers_munge/out/query_tile_cell_map_missing.png' resulting from #350 and #352.
• An updated build status file

[apologies for the PR from my main branch - I forgot to create a new branch on Tallgrass when generating the updated files]

[hcorson-dosch-usgs]

For our record - summary of what was rebuilt following #354 - this all built in 33 minutes:

• The glm_ready_gcm_data_list pattern (all branches)
• The glm_ready_gcm_data_feather pattern (all branches)
• gcm_data_daily_feather_group_by_gcm
• The gcm_nc pattern (all branches)
• query_tile_cell_map_missing_png - ~not sure why this rebuilt, as it skipped glm_ready_gcm_data_cell_info, but it looks unchanged~ rebuilt b/c of committed change to figure sub-title during PR review
• gcm_files_out

[lindsayplatt]

query_tile_cell_map_missing_png - not sure why this rebuilt, as it skipped glm_ready_gcm_data_cell_info, but it looks unchanged

I wonder if query_tile_cell_map_missing_png just hadn't yet been rebuilt on Tallgrass after you did #350 and #352?

[hcorson-dosch-usgs]

I wonder if query_tile_cell_map_missing_png just hadn't yet been rebuilt on Tallgrass after you did #350 and #352?

Ah - I think I found it. I didn't rebuild after you edited the figure sub-title

[lindsayplatt]

Good, not a mysterious rebuild!