Remove second check on row count to stop extract failing on frequently updated large tables

[jrmidkiff]

cco.asset_history may be updated as frequently as every 1-3 minutes around an election, and it uses dbtools postgres extract method to extract the data to S3.

geopetl extract can take 20-40 seconds to extract the table to CSV, by which point a later Jenkins script run on cco.asset_history may have already run and changed the table count. The second check was comparing the CSV row count to the current table row count, which by now may be already outdated.

We already have a 1st check to compare the CSV row count to the table row count at the time of the extraction, so this 2nd check in my opinion adds no value and merely adds the potential for useless exceptions.

If merging to main, please git tag as v1.3.7 and publish a new release, or let me do it