ci: dispatch website rebuild on release-branch doc changes (drop push-based sync)

[Ma77Ball]

What changes were proposed in this PR?

Aligns this repo's CI with the website's new build-time docs sync (merged in apache/incubator-texera-site#72), which pulls each release's docs/ folder straight from this repo's release/vX.Y branches while building the Hugo site.

• Remove sync-docs-to-site.yml. It pushed committed copies of docs/ into apache/incubator-texera-site (content/docs/latest/) on every push to main. The site no longer stores docs in-tree, so this push-based sync is obsolete and would fight the build-time pull.
• Add notify-site-rebuild.yml. When docs change on a release/v* branch, it dispatches the site's existing "Build & Publish Hugo site" workflow (publish-site.yml) on staging via workflow_dispatch, so the edit becomes visible without waiting for an unrelated site commit. The ping is best-effort (continue-on-error) and never fails this repo's CI.

Why not the earlier approach (#6948)?

#6948 was written for an earlier site design that added a repository_dispatch: docs-updated trigger to the site workflow. The design that actually shipped (#72) does not listen for repository_dispatch; it exposes workflow_dispatch. This PR targets what shipped, and needs no change on the site side. #6948 can be closed in favor of this.

Configuration required

Add a repository secret SITE_DISPATCH_TOKEN with Actions: write on apache/incubator-texera-site (a fine-grained PAT scoped to that repo, or a classic PAT with the workflow scope). The old SITE_SYNC_TOKEN (Contents: write) used by the removed workflow can be retired.

Notes / follow-ups

• Targets staging because Issue #71: Refactored DataReader and DataWriter #72 currently lives on the site's staging branch. Once Issue #71: Refactored DataReader and DataWriter #72 reaches the site's main, add a second dispatch on --ref main (production).
• The site's scripts/sync-docs.sh has an explicit VERSIONS list (release/v1.1, release/v1.2); a brand-new release/vX.Y still needs to be added there before it publishes.

Was this PR authored or co-authored using generative AI tooling?

Co-authored with Claude Opus 4.8 in compliance with ASF policy.

[github-actions]

Automated Reviewer Suggestions

Based on the git blame history of the changed files, we recommend the following reviewers:

• No candidates found from git blame history.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.67%. Comparing base (4013ca7) to head (d7bc5bf).

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #7659      +/-   ##
============================================
- Coverage     89.68%   89.67%   -0.01%     
+ Complexity     4399     4397       -2     
============================================
  Files          1175     1175              
  Lines         46979    46979              
  Branches       5265     5265              
============================================
- Hits          42133    42130       -3     
- Misses         3082     3083       +1     
- Partials       1764     1766       +2     

Flag	Coverage Δ
access-control-service	70.00% <ø> (ø)
agent-service	98.62% <ø> (ø)
amber	86.36% <ø> (-0.02%)	⬇️
computing-unit-managing-service	72.46% <ø> (ø)
config-service	77.31% <ø> (ø)
file-service	68.90% <ø> (ø)
frontend	90.70% <ø> (ø)
notebook-migration-service	78.89% <ø> (ø)
pyamber	97.57% <ø> (ø)
workflow-compiling-service	57.89% <ø> (ø)

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

⚠️ Benchmark changes need a look

🟢 0 better · 🔴 6 worse · ⚪ 9 noise (<±5%) · 0 without baseline

Compared against main 4013ca7 benchmarked on this same runner, so the delta is largely free of cross-runner hardware noise. The "7d avg" column still reflects the gh-pages dashboard. Treat <±5% as noise unless repeated.

Dashboard · Run

	config	throughput	MB/s	latency	max Δ latest / 7d
🔴	bs=10 sw=10 sl=64	384	0.234	24,607/34,307/34,307 us	🔴 -7.9% / 🔴 +109.9%
🔴	bs=100 sw=10 sl=64	759	0.463	126,000/183,264/183,264 us	🔴 +28.0% / 🔴 +70.3%
⚪	bs=1000 sw=10 sl=64	884	0.54	1,129,073/1,177,653/1,177,653 us	⚪ within ±5% / 🔴 -14.2%

Baseline details

Latest main 4013ca7 from same runner

config	metric	PR	latest main	7d avg	Δ latest	Δ 7d
bs=10 sw=10 sl=64	throughput	384 tuples/sec	417 tuples/sec	774.89 tuples/sec	-7.9%	-50.4%
bs=10 sw=10 sl=64	MB/s	0.234 MB/s	0.254 MB/s	0.473 MB/s	-7.9%	-50.5%
bs=10 sw=10 sl=64	p50	24,607 us	23,798 us	12,738 us	+3.4%	+93.2%
bs=10 sw=10 sl=64	p95	34,307 us	35,879 us	16,348 us	-4.4%	+109.9%
bs=10 sw=10 sl=64	p99	34,307 us	35,879 us	18,848 us	-4.4%	+82.0%
bs=100 sw=10 sl=64	throughput	759 tuples/sec	805 tuples/sec	1,005 tuples/sec	-5.7%	-24.5%
bs=100 sw=10 sl=64	MB/s	0.463 MB/s	0.492 MB/s	0.613 MB/s	-5.9%	-24.5%
bs=100 sw=10 sl=64	p50	126,000 us	120,286 us	100,970 us	+4.8%	+24.8%
bs=100 sw=10 sl=64	p95	183,264 us	143,136 us	107,605 us	+28.0%	+70.3%
bs=100 sw=10 sl=64	p99	183,264 us	143,136 us	116,429 us	+28.0%	+57.4%
bs=1000 sw=10 sl=64	throughput	884 tuples/sec	900 tuples/sec	1,030 tuples/sec	-1.8%	-14.2%
bs=1000 sw=10 sl=64	MB/s	0.54 MB/s	0.549 MB/s	0.629 MB/s	-1.6%	-14.1%
bs=1000 sw=10 sl=64	p50	1,129,073 us	1,106,750 us	991,433 us	+2.0%	+13.9%
bs=1000 sw=10 sl=64	p95	1,177,653 us	1,218,730 us	1,036,668 us	-3.4%	+13.6%
bs=1000 sw=10 sl=64	p99	1,177,653 us	1,218,730 us	1,070,470 us	-3.4%	+10.0%

Raw CSV

config_idx,batch_size,schema_width,string_len,num_batches,total_ms,total_tuples,total_bytes,tuples_per_sec,mb_per_sec,lat_p50_us,lat_p95_us,lat_p99_us
0,10,10,64,20,521.09,200,128000,384,0.234,24607.44,34306.50,34306.50
1,100,10,64,20,2634.00,2000,1280000,759,0.463,126000.49,183264.17,183264.17
2,1000,10,64,20,22616.13,20000,12800000,884,0.540,1129072.56,1177653.04,1177653.04