[HUDI-7242] Avoid unnecessary bigquery table update when using sync tool

[jp0317]

Change Logs

The PR added a table schema update step for bigquery sync tool. It seems there're two issues (this PR focuses on the 1st one):

1. When it reform the schema which is then compared to the bq table schema, the reformed schema puts partition fields in the beginning, while the bq table schema by default has partition fields at the end. So it unnecessarily triggers a schema update due to to order difference.

2. Though the sync tool for 0.14.0 does not support big lake connection id (there's a recent PR last month adding this support), a user can still recreate their table manually by adding connection id. The table update is adding the new schema into. external table definition. This does not work for biglake tables, and will cause error: "Schema can be specified only on the Table.Schema field for external tables with an associated connection_id but schema was provided on Table.Externaldataconfig.Schema".

Impact

Avoid the unnecessary table update.

Risk level (write none, low medium or high below)

low. It only corrects the order of fields.

Documentation Update

Describe any necessary documentation update if there is any new feature, config, or user-facing change

• The config description must be updated if new configs are added or the default value of the configs are changed
• Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
  ticket number here and follow the instruction to make
  changes to the website.

Contributor's checklist

• Read through contributor's guide
• Change Logs and Impact were stated clearly
• Adequate tests were added if applicable
• CI passed

[danny0405]

cc @the-other-tim-brown Looks a reasonable fix~

[hudi-bot]

CI report:

• 5d4608d Azure: FAILURE

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build

[the-other-tim-brown]

LGTM! Thanks for catching this @jp0317