try to fix flaky yaml jdbc tests

[derrickaw]

1. Write data to jdbc before starting the pipeline so that there is data to read from.
2. Add retries
3. Specify a higher grade machine
4. Cut out unnecessary driver classes and type parameters
5. Add 2s timeout to save some time

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 38.05%. Comparing base (4d01025) to head (ac060a1).
⚠️ Report is 3 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (4d01025) and HEAD (ac060a1). Click for more details.

HEAD has 5 uploads less than BASE

Flag	BASE (4d01025)	HEAD (ac060a1)
	7	2

Additional details and impacted files

@@              Coverage Diff              @@
##               main    #4295       +/-   ##
=============================================
- Coverage     56.34%   38.05%   -18.30%     
+ Complexity     7855      513     -7342     
=============================================
  Files          1154      195      -959     
  Lines         73220    11799    -61421     
  Branches       8585     1190     -7395     
=============================================
- Hits          41257     4490    -36767     
+ Misses        29177     6941    -22236     
+ Partials       2786      368     -2418     

Components	Coverage Δ
spanner-templates	∅ <ø> (∅)
spanner-import-export	∅ <ø> (∅)
spanner-live-forward-migration	∅ <ø> (∅)
spanner-live-reverse-replication	∅ <ø> (∅)
spanner-bulk-migration	∅ <ø> (∅)
gcs-spanner-dv	∅ <ø> (∅)
see 984 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.