Fix last references to old greencheck_2021 table

docs/understanding-the flow-of-a-greencheck.md

@@ -23,7 +23,7 @@ sequenceDiagram
     Django Web->>+RabbitMQ: Queue domain for logging
 ```
 
-In most cases we try to find a result we can return quickly, and check in a local cache table called `greendomain`, described by the GreenDomain model. Assuming we find a result in the database, we put the checked domain on a Rabbit MQ queue, so that a separate worker process can update to the cache to record the time of the check, and so it can write the check result to a logging table, currently named `greencheck_2021`, and represented by the Greencheck model.
+In most cases we try to find a result we can return quickly, and check in a local cache table called `greendomain`, described by the GreenDomain model. Assuming we find a result in the database, we put the checked domain on a Rabbit MQ queue, so that a separate worker process can update to the cache to record the time of the check, and so it can write the check result to a logging table, currently named `greencheck`, and represented by the Greencheck model.
 
 _Note: See the model definitions Greencheck and GreenDomain for the definitive listing of the names the tables we write to - they have changed over time._
 

one_day_to_parquet.py

@@ -122,7 +122,7 @@ def backup_day_to_parquet(target_date: datetime.date):
     # and avoid clashes
     with tempfile.TemporaryDirectory() as tmpdir:
         date_string = target_date.strftime("%Y-%m-%d")
-        greencheck_table = "greencheck_2021"
+        greencheck_table = "greencheck"
 
         csv_path = f"{tmpdir}/{date_string}.local_file.csv"
         parquet_path = f"{tmpdir}/{date_string}.zstd.parquet"