Patch to hide "bad lon" messages when using maskmap

- Using a mask_table to mask out processors necessarily means that
  some geographic coordinate data is not known in all halo-regions.
- The iceberg code scans the geographic coordinate data and reports
  points that have "suspect" values. Using a mask_table caused a
  lot of messages to be written.
- I've disable this sanity check when a mask_table is being used.
- No answer changes.

ice_bergs.F90

@@ -2764,10 +2764,12 @@ subroutine icebergs_init(bergs, &
       if (grd%lat(i,j).gt.900.) grd%lat(i,j)=2.*grd%lat(i,j+1)-grd%lat(i,j+2)
   enddo; enddo
 
-  do j=grd%jsd,grd%jed; do i=grd%isd,grd%ied
+  if (.not. present(maskmap)) then ! Using a maskmap causes tickles this sanity check
+    do j=grd%jsd,grd%jed; do i=grd%isd,grd%ied
       if (grd%lon(i,j).gt.900.) write(stderrunit,*) 'bad lon: ',mpp_pe(),i-grd%isc+1,j-grd%jsc+1,grd%lon(i,j)
       if (grd%lat(i,j).gt.900.) write(stderrunit,*) 'bad lat: ',mpp_pe(),i-grd%isc+1,j-grd%jsc+1,grd%lat(i,j)
-  enddo; enddo
+    enddo; enddo
+  endif
 
   ! Sanitize lon for the tile (need continuous longitudes within one tile)
   j=grd%jsc; do i=grd%isc+1,grd%ied