Bug: Log files can become too large

[2320sharon]

A user recently reported that their log file was over 3GB large when they used the zoo workflow. This is not acceptable.
I suspect the fact that the reference shorelines are printed to the log file is partially to blame. Try to ensure the log file doesn't get too large by doing the following:

• Don't print the reference shorelines

• Remove unneeded logs

• print a summary of the shoreline dictionary instead of the entire thing

• print a summary of the transect dictionary instead of the entire thing
  -- print unique sats
  -- length of each array
  -- 10 unique elements of each array

• fix the repr for the ROI, Shoreline, Transect

• minimize prints on the on_click handlers

• dont print .update_roi_html

• fix on click handler to not print entire gdf just the roi id clicked

• fix load feature and add_feature_on_map on map to print just the head and the types of geometries

• have set settings print the kwargs printed in

[2320sharon]

Other Maintenance Tasks

• No longer download tier 2 imagery

• No longer save blank transect shoreline intersections to time series csv files

[2320sharon]

Closed in version 1.1.23