use spatial_extent and datetime_extent everywhere

[hrodmn]

What I am changing

• We added the spatial_extent and datetime_extent parameters to register_collection_catalog but they were only getting used in one of the calls to the function. After deploying tipg again on a database with some really large tables with spatial and temporal columns I realized that the extent calculations were still getting run but not at application startup!

How I did it

• pass the spatial_extent and datetime_extent settings to all calls to register_collection_catalog (not just the first one).

Related Issues

• make calculating spatial/datetime extents optional #143