specify the columns in the backfill procedures, makes sure the script…

[kingman]

…s are executable with a previous created feature table

Description

When the backfill scripts changes and the user try to re-run a backfill with an existing feature table, they will get Query error: Inserted row has wrong column count error. this also ensures that the columns are mapped correctly

How has this been tested?

in the integration test environment

Please explain how you have tested the new changes.

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have successfully run the E2E tests, and have included the links to the pipeline runs below
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have updated any relevant documentation to reflect my changes
• I have assigned a reviewer and messaged them

Pipeline run links:

[chmstimoteo]

LGTM!