feat: Arizona LiveView routing integration

[Taure]

Summary

• Add nova_arizona bridge module for rendering Arizona LiveView views through Nova's request pipeline
• New route protocol #{protocol => liveview} — views go through the full plugin/security middleware chain
• Auto-registers /live WebSocket endpoint (configurable via arizona_live_path app env) when liveview routes are present
• Arizona remains an optional dependency — no runtime calls unless liveview routes are defined

Route syntax

routes(_Env) ->
    [#{prefix => "", routes => [
        {"/", my_home_view, #{protocol => liveview}},
        {"/counter", my_counter_view, #{protocol => liveview, mount_arg => #{initial => 0}}}
    ]}].

How it works

1. During route compilation, liveview routes register a Nova callback closure that calls nova_arizona:render_view/3 for HTTP rendering
2. Each liveview route is also accumulated via register_view/3
3. After compilation, finalize/1 builds Arizona's Cowboy dispatch table (persistent_term:put(arizona_dispatch, ...)) so arizona_websocket can resolve views for client-side reactivity
4. The /live WebSocket endpoint is added as a raw Cowboy handler (#cowboy_handler_value{})

Test plan

• Verify compilation passes with xref and dialyzer (no Arizona dependency needed at compile time)
• Test with a project that includes Arizona — confirm HTTP render and WebSocket upgrade work
• Verify projects without Arizona are unaffected (no-op when no liveview routes)

🤖 Generated with Claude Code