Also sync neighborhood boundary files for analysis fixture

The boundary file for a neighborhood doesn't get used by the front end,
but it does get used when you run a new analysis for that neighborhood.
So they also need to be synced into the dev S3 bucket when setting up a
new dev instance and installing hte fixture.
I've put the files in the 'test-pfb-inputs' bucket, this adds a command
to 'update' to sync them to the dev bucket, along with the results files.

scripts/update

@@ -78,6 +78,9 @@ function run_data_fixtures() {
         aws --profile pfb s3 sync --quiet \
             "s3://test-pfb-inputs/fixture_results_files/" \
             "s3://${DEV_USER}-pfb-storage-us-east-1/results/"
+        aws --profile pfb s3 sync --quiet \
+            "s3://test-pfb-inputs/fixture_neighborhood_boundaries/" \
+            "s3://${DEV_USER}-pfb-storage-us-east-1/neighborhood_boundaries/"
     fi
     docker compose stop database
 }