refactor(fullcalendar): revert Angular options workaround now that the emitter aliases template-referenced imports

FullCalendarAllSlotsDemo previously hoisted the passthrough :options object into
a `const calendarOptions` <script> declaration purely to pin the
`@fullcalendar/list` default import — Angular AOT would otherwise tree-shake an
import whose only reference lived inside the template-binding object literal,
leaving listPlugin undefined and crashing FullCalendar's plugin-hook builder.

The Angular emitter now aliases a <script> value-import referenced in a template
expression to a `protected readonly listPlugin = listPlugin` component field, so
the natural inline form is correct on all six targets. Pass the options inline
again (:options="{ ..., plugins: [listPlugin] }") and keep the
`import listPlugin from '@fullcalendar/list'`. The VR full-calendar-slots
[angular] cell passes with the inline form end-to-end.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: serpentblade

examples/demos/FullCalendarAllSlotsDemo.rozie

@@ -69,21 +69,17 @@
 // consumer imports it and passes it through the wrapper's now-merged
 // :options.plugins, which is the exact opt-in plugin-extension mechanism this
 // demo exercises.
+//
+// `listPlugin` is referenced INLINE in the template's :options binding below —
+// the natural authoring form. This is now correct on all six targets: the
+// Angular emitter aliases a <script> value-import referenced in a template
+// expression to a `protected readonly listPlugin = listPlugin` component field,
+// so the bare template reference resolves against the instance AND the import
+// stays live (Angular AOT would otherwise tree-shake an import whose only use is
+// in the separate template compilation context). The other five targets share
+// one module scope and never needed the workaround.
 import listPlugin from '@fullcalendar/list'
 
-// Build the passthrough :options object in the SCRIPT (not inline in the
-// template) so the `listPlugin` import is referenced from a <script> statement.
-// Angular's AOT pipeline tree-shakes a default import that is ONLY referenced
-// inside a template-binding object literal — leaving `listPlugin` undefined at
-// runtime and crashing FullCalendar's plugin-hook builder. Referencing it here
-// pins the import on every target (the other five are unaffected either way).
-const calendarOptions = {
-  weekNumbers: true,
-  dayMaxEvents: 2,
-  businessHours: { startTime: '09:00', endTime: '17:00' },
-  plugins: [listPlugin],
-}
-
 // All seed events land on a SINGLE pinned day (2026-06-15) so that — with the
 // passthrough dayMaxEvents: 2 — the day overflows past 2 and the engine renders
 // a `.fc-more-link` (which routes through the moreLink portal-slot). Fixed ISO
@@ -160,7 +156,7 @@ const remount  = () => { $data.calendarMounted = true }
       :height="480"
       :selectable="true"
       :editable="true"
-      :options="calendarOptions"
+      :options="{ weekNumbers: true, dayMaxEvents: 2, businessHours: { startTime: '09:00', endTime: '17:00' }, plugins: [listPlugin] }"
       @eventMouseEnter="onEventMouseEnter"
       @eventMouseLeave="onEventMouseLeave"
       @unselect="onUnselect"