Spark: Fix wap branch metadata delete on the wrong branch

[yingjianwu98]

SparkTable.deleteWhere() and canDeleteWhere() do not resolve the WAP (Write-Audit-Publish) branch from the session configuration. When a user sets spark.wap.branch and performs a metadata-level delete, both the scan and the commit incorrectly target the main branch instead of the WAP branch.

FordeleteWhere(), I think it's a recent regression from this PR. The new change doesn't resolve to the right branch in the new extension rule for Spark 4.1. I don't see an easy way to resolve this issues in the resolveBranch Rule as I believe OptimizeMetadataOnlyDeleteFromTable optimizer rule will discard ResolveBranch rule and then trigger deleteWhere() which currently doesn't respect the wap branch if specified.

For canDeleteWhere(), this is an existing issue across all spark version and I have been working on a fix here
#15512

This causes two issues:

• canDeleteWhere() scans the wrong branch's files, so it cannot correctly determine whether the delete can be resolved at the metadata level
• deleteWhere() commits the delete to main instead of the WAP branch, silently dropping the delete

Fix:

• Use determineReadBranch() in canDeleteWhere() to scan the correct branch
• Use determineWriteBranch() in deleteWhere() to commit to the correct branch