chore(pybuilder): aggregate PyBuilder at root and add API spec for non-macro pieces

[Yicong-Huang]

What changes were proposed in this PR?

Three closely related changes scoped to common/pybuilder:

1. Add PyBuilder to the root TexeraProject aggregate(...), grouped under "common libraries" alongside Auth, Config, DAO, WorkflowCore, and WorkflowOperator (alphabetized within each group). Before this PR, PyBuilder was the only sbt project defined but not aggregated, so sbt test and sbt scalafmtCheckAll from the repo root silently skipped it. CI still ran PyBuilder/jacoco explicitly, so coverage reporting was unaffected, but the local/CI matrix mismatch was confusing.

2. Apply scalafmt to four pre-existing PyBuilder files (BoundaryValidator.scala, EncodableInspector.scala, PythonTemplateBuilder.scala, PythonTemplateBuilderSpec.scala). scalafmtCheckAll only iterates over aggregated sub-projects, so change 1 brought PyBuilder under the format gate for the first time and surfaced debt that had been accumulating invisibly since the project was introduced. Reformatting these files is the necessary follow-on for change 1 to leave CI green; the diffs are purely scaladoc-star indentation and multi-line case-class parameter alignment, no semantic changes.

3. Add PythonTemplateBuilderApiSpec covering non-macro pieces of PythonTemplateBuilder that PythonTemplateBuilderSpec only touches incidentally — factory constructors, render-mode singletons, renderer behavior in both modes, fromInterpolated precondition, +(String) UnsupportedOperationException, and render() CR/CRLF normalization. Also pins current PythonLexerUtils behavior on Python triple-quoted strings (the lexer is intentionally conservative and not triple-quote-aware; pinned so a future triple-quote-aware change trips the spec deliberately).

Any related issues, documentation, discussions?

Resolves #5023

How was this PR tested?

sbt PyBuilder/test — 125 tests pass (32 new). sbt PyBuilder/jacoco line coverage went from 30.12% to 31.73% and method coverage from 13.17% to 15.30% (6 newly covered methods); the rest of PythonTemplateBuilder.scala is the pybImpl macro body which jacoco cannot instrument at runtime. sbt scalafmtCheckAll now passes cleanly with PyBuilder included.

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

Generated-by: Claude Opus 4.7 (1M context)

[codecov-commenter]

Codecov Report

❌ Patch coverage is 20.00000% with 16 lines in your changes missing coverage. Please review.
✅ Project coverage is 42.70%. Comparing base (0e9c617) to head (bba989b).

Files with missing lines	Patch %	Lines
...che/texera/amber/pybuilder/BoundaryValidator.scala	0.00%	9 Missing ⚠️
...he/texera/amber/pybuilder/EncodableInspector.scala	0.00%	4 Missing ⚠️
...texera/amber/pybuilder/PythonTemplateBuilder.scala	57.14%	3 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #5024      +/-   ##
============================================
+ Coverage     42.48%   42.70%   +0.22%     
+ Complexity     2185     2184       -1     
============================================
  Files          1045     1031      -14     
  Lines         39878    38094    -1784     
  Branches       4205     4004     -201     
============================================
- Hits          16941    16268     -673     
+ Misses        21875    20807    -1068     
+ Partials       1062     1019      -43     

Flag	Coverage Δ		*Carryforward flag
access-control-service	39.88% <ø> (ø)
agent-service	33.72% <ø> (ø)		Carriedforward from 16d3c6a
amber	43.24% <20.00%> (+<0.01%)	⬆️
computing-unit-managing-service	0.00% <ø> (ø)
config-service	0.00% <ø> (ø)
file-service	32.10% <ø> (ø)
frontend	32.99% <ø> (-0.52%)	⬇️	Carriedforward from 16d3c6a
python	88.86% <ø> (-0.04%)	⬇️	Carriedforward from 16d3c6a
workflow-compiling-service	47.72% <ø> (ø)

*This pull request uses carry forward flags. Click here to find out more.

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

🚀 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.

[Copilot]

Pull request overview

This PR aligns local sbt test behavior with CI by aggregating the PyBuilder subproject under the root TexeraProject, and expands unit coverage for the non-macro API surface of PythonTemplateBuilder (factories, render modes, render normalization, concatenation behavior, and preconditions).

Changes:

• Add PyBuilder to the root SBT aggregate list so root-level sbt test includes PyBuilder tests.
• Add PythonTemplateBuilderApiSpec to directly test non-macro API behaviors and pin current lexer behavior around Python triple quotes.
• Apply formatting-only refactors in existing Scala sources/specs (no intended behavioral changes).

Reviewed changes

Copilot reviewed 3 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
build.sbt	Adds PyBuilder to TexeraProject.aggregate(...) to ensure root builds/tests include it.
common/pybuilder/src/test/scala/org/apache/texera/amber/pybuilder/PythonTemplateBuilderApiSpec.scala	New spec covering non-macro PythonTemplateBuilder API and pinning lexer behavior.
common/pybuilder/src/test/scala/org/apache/texera/amber/pybuilder/PythonTemplateBuilderSpec.scala	Formatting adjustments only.
common/pybuilder/src/main/scala/org/apache/texera/amber/pybuilder/PythonTemplateBuilder.scala	Formatting/minor refactor of chaining; no functional changes intended.
common/pybuilder/src/main/scala/org/apache/texera/amber/pybuilder/EncodableInspector.scala	Formatting-only adjustments.
common/pybuilder/src/main/scala/org/apache/texera/amber/pybuilder/BoundaryValidator.scala	Formatting-only adjustments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[bobbai00]

I see lots of formatting change. Are they needed ? If not can you revert them ?

Other parts LGTM

[Yicong-Huang]

I see lots of formatting change. Are they needed ? If not can you revert them ?

Other parts LGTM

I explained in the PR description already ;)