Support new lists in Cloud Build sync objects job

[CydeWeys]

Update release/db-object-updater/sync_db_objects.sh to pass --upsert when running update_premium_list or update_reserved_list so newly added lists are created automatically without shell fallback or currency parsing.

Also reorder release/cloudbuild-sync-db-objects.yaml so that premium and reserved lists are synced before configure_tld runs, ensuring newly created lists exist in the database before TLD configurations reference them, and add unit tests for sync_db_objects.sh in SyncDbObjectsTest.

Note: This PR is stacked on #3248 (update-list-upsert) and should be merged and deployed only after #3248 is deployed to production.

BUG=http://b/569977604

---

This change is 

[gbrodman]

@gbrodman reviewed 2 files and all commit messages, and made 2 comments.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on CydeWeys).

---

release/db-object-updater/sync_db_objects.sh line 42 at r1 (raw file):

  if [[ -e "${FILE}" ]]; then
    echo "${FILE}"
    if ! java -jar /nomulus.jar -e "${nomulus_env}" \

we should capture the output here and only attempt the create-list fallback when the output tells us that the list doesn't exist

for other failures, just error out with that failure

---

release/db-object-updater/sync_db_objects.sh line 53 at r1 (raw file):

        echo "update_premium_list failed for ${FILE}, attempting" \
          "create_premium_list fallback with currency ${CURRENCY:-USD}..."
        java -jar /nomulus.jar -e "${nomulus_env}" \

what happens if this fails? i worry we'd be swallowing any failure