Implement SeaDatabricksClient (Complete Execution Spec)

[varun-edachali-dbx]

What type of PR is this?

• Feature

Description

• Implement execution relevant methods in SeaDatabricksClient as defined in the DatabricksClient interface.
• Does not implement metadata relevant methods.

How is this tested?

• Unit tests
• E2E Tests
• Manually - using the test scripts to be introduced in Introduce manual SEA test scripts for Exec Phase  #589
• N/A

The coverage of SeaDatabricksClient by test_sea_backend.py's unit tests are as below.

Module	Statements	Missing	Coverage	Notes
backend.py (SeaDatabricksClient class)	167	2	99%	Missing lines are TYPE_CHECKING imports (lines 16-17) which are not meant to be covered in runtime tests

Related Tickets & Documents

https://docs.google.com/document/d/1Y-eXLhNqqhrMVGnOlG8sdFrCxBTN1GdQvuKG4IfHmo0/edit?usp=sharing

[jayantsing-db]

some minor questions/suggestions. Rest LGTM

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).