fix/direct-selectra-init-timing

[BrijeshSajeev]

• This release improves reliability for direct <select x-selectra> usage in real applications (including Rails/Turbo environments).
• Selectra now performs <select> auto-wrapping synchronously during plugin registration, ensuring initialization happens before Alpine processes the DOM.
• A fallback alpine:init listener is retained for late-parsed content.
• Result: direct-on-select integration is now consistent and no longer depends on event timing.

[BrijeshSajeev]

Auto-wrapping is important because it preserves both HTML validity and Selectra behavior while keeping authoring simple.

Why Auto-Wrapping Matters

• <select> cannot contain the Selectra UI markup.
  The Selectra template includes <div>, <input>, <template>, <svg>, etc. Those are invalid children of <select>, so browsers strip/reparent them unpredictably.

• You still need the native <select> for forms.
  Selectra reads options from the native select, hides it, syncs selected values, and lets normal form submission work. Auto-wrapping gives you a container for the custom UI while preserving the original select.

• Better DX for Rails/server-rendered forms.
  Users can write x-selectra directly on generated <select> fields (from f.select / helpers) without manually adding wrapper markup around every field.

• Prevents timing fragility.
  Running wrap logic during plugin registration ensures wrapping is done before Alpine walks the DOM. This avoids missed initialization in environments like Turbo/deferred scripts.