Fix github action concurrency to cancel old commit on new push

[Abacn]

apply same fix of #1595 to the other two workflows

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.29%. Comparing base (40e1a8b) to head (653a4d5).
Report is 6 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #2193      +/-   ##
============================================
+ Coverage     46.97%   51.29%   +4.31%     
+ Complexity     4047     1651    -2396     
============================================
  Files           876      448     -428     
  Lines         52203    24124   -28079     
  Branches       5502     2371    -3131     
============================================
- Hits          24524    12374   -12150     
+ Misses        25922    11030   -14892     
+ Partials       1757      720    -1037     

Components	Coverage Δ
spanner-templates	70.43% <ø> (+1.50%)	⬆️
spanner-import-export	∅ <ø> (∅)
spanner-live-forward-migration	76.54% <ø> (ø)
spanner-live-reverse-replication	78.80% <ø> (ø)
spanner-bulk-migration	87.94% <ø> (ø)

see 446 files with indirect coverage changes

[Abacn]

R: @VardhanThigle @damccorm

[damccorm]

Thanks!

[damccorm]

Test failures are clearly unrelated to this PR, but I'll try rerunning to get a green signal if we can - seems unlikely though given https://github.com/GoogleCloudPlatform/DataflowTemplates/actions/workflows/spanner-pr.yml

[damccorm]

Test failures are clearly unrelated to this PR, but I'll try rerunning to get a green signal if we can - seems unlikely though given https://github.com/GoogleCloudPlatform/DataflowTemplates/actions/workflows/spanner-pr.yml

To be clear, we shouldn't block merging on this

[Abacn]

SpannerToSourceDbCustomTransformationIT
is a known flaky test and is acknowledged by owner team, see #2191 (comment)

[damccorm]

Sounds good, lets just merge