refactor(builder): pass nuxt options to template as nuxtOptions

[clarkdo]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Fixes: #5783
Related to #5730

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly. (PR: #)
• I have added tests to cover my changes (if not applicable, please state why)
• All new and existing tests are passing.

[codecov-io]

Codecov Report

Merging #5792 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #5792   +/-   ##
=======================================
  Coverage   95.64%   95.64%           
=======================================
  Files          82       82           
  Lines        2662     2662           
  Branches      682      682           
=======================================
  Hits         2546     2546           
  Misses         98       98           
  Partials       18       18

Flag	Coverage Δ
#e2e	100% <ø> (ø)	⬆️
#fixtures	50.71% <ø> (ø)	⬆️
#unit	92.59% <ø> (ø)	⬆️

Impacted Files	Coverage Δ
packages/builder/src/builder.js	100% <ø> (ø)	⬆️
packages/builder/src/context/template.js	100% <ø> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 59071e4...8b78986. Read the comment docs.

[pi0]

LGTM

[galvez]

Nice!

[pi0]

For docs, I suggest keeping this new (feature) as undocumented. In any stage, we may change the config interface in an incompatible way and this may break users. Maybe we can suggest always cherry-picking needed options into template options param when needed.

[clarkdo]

@pi0 Agree