fix: Add missing license headers to Docs

[parshimers]

What changes were proposed in this PR?

This just adds missing license headers to the markdown documentation and other markdown files in the source. It also enables checking of markdown files for these headers via skywalking eyes by changing the .licenserc config.

Performance Impact

None- these are headers in doc files.

Any related issues, documentation, discussions?

Closes #6955
Would be a follow on to the inital addition of license headers to other source files, e.g. #3415 and #4135

related vote thread: https://lists.apache.org/thread/x12wsodfyhqs1fxr95fw6ngyw1xxn5jk

How was this PR tested?

If the CI check passes it should be fine. I only allowed one file which I think is not under ASL2, but mentioned elsewhere

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

No.

[github-actions]

👋 Thanks for your first contribution to Texera, @parshimers!

If you're looking for a good place to start, browse issues labeled starter-task; they're scoped to be approachable for newcomers.

You can drive common housekeeping yourself by commenting one of these commands on its own line:

• Issues. Comment /take to assign an open issue to yourself, or /untake to release it. You can find unclaimed work with the search filter is:issue is:open no:assignee.
• Sub-issues. To link issues into a parent/child hierarchy, comment /sub-issue #5166 #5222 on the parent to attach those children (or /unsub-issue #5166 #5222 to detach them). From a child issue, comment /parent-issue #5166 to set its parent, or /unparent-issue to clear it (the current parent is detected automatically). References may be written as #5166 or as a bare 5166; cross-repository references are not supported.
• Pull requests (author only). Comment /request-review @user to request a review from someone, or /unrequest-review @user to withdraw that request.

Each command must match exactly: /take this will not work, only /take does. For the full contribution flow, see CONTRIBUTING.md.

[github-actions]

Automated Reviewer Suggestions

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

• Contributors with relevant context: @Ma77Ball, @Yicong-Huang, @aglinxinyuan
  You can notify them by mentioning @Ma77Ball, @Yicong-Huang, @aglinxinyuan in a comment.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.96%. Comparing base (bfe2b53) to head (09a7cb5).

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #6958      +/-   ##
============================================
- Coverage     78.99%   78.96%   -0.03%     
+ Complexity     3789     3781       -8     
============================================
  Files          1160     1160              
  Lines         46105    46105              
  Branches       5115     5115              
============================================
- Hits          36420    36409      -11     
- Misses         8067     8072       +5     
- Partials       1618     1624       +6     

Flag	Coverage Δ
access-control-service	70.00% <ø> (ø)
agent-service	76.76% <ø> (ø)
amber	72.14% <ø> (-0.07%)	⬇️
computing-unit-managing-service	20.49% <ø> (ø)
config-service	66.66% <ø> (ø)
file-service	67.21% <ø> (ø)
frontend	82.99% <ø> (ø)
notebook-migration-service	78.94% <ø> (ø)
pyamber	95.38% <ø> (ø)
workflow-compiling-service	26.31% <ø> (ø)

☔ 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 · 🔴 9 worse · ⚪ 6 noise (<±5%) · 0 without baseline

Compared against main bfe2b53 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	430	0.262	22,835/31,887/31,887 us	🔴 -5.4% / 🔴 +101.8%
🔴	bs=100 sw=10 sl=64	922	0.563	107,229/140,615/140,615 us	🔴 +15.2% / 🔴 +31.0%
🔴	bs=1000 sw=10 sl=64	1,079	0.658	927,561/1,042,447/1,042,447 us	🔴 +9.0% / 🟢 -5.5%

Baseline details

Latest main bfe2b53 from same runner

config	metric	PR	latest main	7d avg	Δ latest	Δ 7d
bs=10 sw=10 sl=64	throughput	430 tuples/sec	453 tuples/sec	787.55 tuples/sec	-5.1%	-45.4%
bs=10 sw=10 sl=64	MB/s	0.262 MB/s	0.277 MB/s	0.481 MB/s	-5.4%	-45.5%
bs=10 sw=10 sl=64	p50	22,835 us	23,008 us	12,255 us	-0.8%	+86.3%
bs=10 sw=10 sl=64	p95	31,887 us	32,114 us	15,802 us	-0.7%	+101.8%
bs=10 sw=10 sl=64	p99	31,887 us	32,114 us	19,008 us	-0.7%	+67.8%
bs=100 sw=10 sl=64	throughput	922 tuples/sec	977 tuples/sec	997.81 tuples/sec	-5.6%	-7.6%
bs=100 sw=10 sl=64	MB/s	0.563 MB/s	0.597 MB/s	0.609 MB/s	-5.7%	-7.6%
bs=100 sw=10 sl=64	p50	107,229 us	99,749 us	100,690 us	+7.5%	+6.5%
bs=100 sw=10 sl=64	p95	140,615 us	122,045 us	107,316 us	+15.2%	+31.0%
bs=100 sw=10 sl=64	p99	140,615 us	122,045 us	113,823 us	+15.2%	+23.5%
bs=1000 sw=10 sl=64	throughput	1,079 tuples/sec	1,108 tuples/sec	1,030 tuples/sec	-2.6%	+4.7%
bs=1000 sw=10 sl=64	MB/s	0.658 MB/s	0.676 MB/s	0.629 MB/s	-2.7%	+4.6%
bs=1000 sw=10 sl=64	p50	927,561 us	897,899 us	981,213 us	+3.3%	-5.5%
bs=1000 sw=10 sl=64	p95	1,042,447 us	956,493 us	1,027,605 us	+9.0%	+1.4%
bs=1000 sw=10 sl=64	p99	1,042,447 us	956,493 us	1,055,466 us	+9.0%	-1.2%

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,465.58,200,128000,430,0.262,22834.89,31886.59,31886.59
1,100,10,64,20,2168.65,2000,1280000,922,0.563,107228.71,140615.08,140615.08
2,1000,10,64,20,18543.94,20000,12800000,1079,0.658,927561.20,1042446.73,1042446.73

[parshimers]

I'm a little confused about how https://github.com/apache/incubator-texera-site and the content under docs/ interact. Is the content under docs/ just a copy that is never published to https://texera.apache.org/docs/latest/ ? Or is there some way the content will be copied/referenced at a tagged version for each release or something along those lines?
The reason I ask is I'd like to be sure the way the license headers are added doesn't make anything that ends up parsing the markdown break. AFAIK there's no universally accepted way of adding comments to markdown itself. Certainly if it's going to be rendered into a page HTML seems like a sensible option but I don't know that this is always the case.

[Yicong-Huang]

Thanks @parshimers for the question. @Ma77Ball please explain the current doc setup and the plan forward.

[Yicong-Huang]

Thanks @parshimers for the fix! Added two comments inline.

[xuang7]

The PR looks good to me. Thanks for the fix! Once it is ready to merge, we can backport it to the release/v1.2 branch.

[parshimers]

The PR looks good to me. Thanks for the fix! Once it is ready to merge, we can backport it to the release/v1.2 branch.

Sounds good. I can also move it to a more appropriate branch if that makes things cleaner. Do sbt releases work kind of like maven-release-plugin ones, where you merge back in the release branch to advance the version? Or does the RC branch basically just become the release branch and never gets merged back?

[Yicong-Huang]

@parshimers we don't do sbt/maven release for texera. We release the docker images instead. But the merging processing is similar: we merge to main then backport to release branches like release/v1.2, and the next RC will cut from the release branch.

We are also ongoing automatic backport CI changes in the recent 1~2 days, you will see automations to help you backport with simply adding the release/v1.2 label on this PR targeting main. If the auto backport fails (e.g., due to conflict or failed CI), a backport PR targeting the release branch will be opened so you can resolve the issue and merge there.

[github-actions]

Backport PR opened: draft #6982 (#6982) to release/v1.2, assigned to @parshimers — needs manual work because the cherry-pick conflicts.