[HUDI-8331] Remove excessive table validity check

[CTTY]

Change Logs

Remove TableNotFoundException#checkTableValidity and its usages.

This method is excessive because Hudi should just fail later on if this path is not valid/does not exist. This check is also problematic because it adds excessive FS calls, which can be very expensive when interacting with object stores like S3.

Impact

none

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

low

Documentation Update

none

• 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]

+1, makes sense.

[hudi-bot]

CI report:

• 1237d84 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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

[yihua]

LGTM