feat(view-controls): add headless view-controls docs and Nuxt pager wiring

[StirStudios]

Summary

• add headless, UI-agnostic view-controls guidance in playground/VIEW_CONTROLS.md
• add useDrupalCeViewControls example composable for filtering, sorting, and pagination state
• wire drupal-view--default pagination to route query updates
• update DrupalViewsPagination to use NuxtLink-based page navigation with update:current support
• harden test/e2e/errorhandling.test.ts against transient socket startup failures in CI

Why

• provides a documented reference implementation teams can reuse without locking into a specific UI library
• keeps pagination URL-driven and shareable while preserving component-level update events
• reduces flaky CI failures caused by intermittent app-start timing issues during e2e fetch calls

Scope

• playground/docs + pagination component + related e2e reliability improvements
• no API contract changes in the module runtime

Validation

• CI e2e suite for this PR (Node 22)

[fago]

wow, this seems pretty interesting. As I understand this makes pagination all client-side driven? but wouldn'T that be the case with regular nuxt-links anyway?

Could you share a bit more on the why, what this enables over the existing pagination?

[StirStudios]

For us, this goes beyond just pagination, and also beyond treating a View as a standalone page.

We embed Views as paragraph bundles, which means we can have multiple Views on a single page — each needing its own pagination and filtering.

This is how we’re using it now:

https://github.com/StirStudios/nuxtjs-drupal-stir/blob/main/app/components/global/drupal-view–default.vue
https://github.com/StirStudios/nuxtjs-drupal-stir/blob/main/app/composables/useDrupalViewControls.ts

With that setup, you can support much more complex filtering.