[Bug Fix] Emit type="button" for any non-anchor TabsTrigger

Tie the `type="button"` attribute to the element actually rendered
(`unless @as == :a`) instead of an exact `@as == :button` check. An
unexpected/mistyped `as:` value fell through to the `<button>` branch
without a type, which defaults to `type="submit"` and could trigger
accidental form submission. Issue identified by cubic.

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

Author: jacksonpires

gem/lib/ruby_ui/tabs/tabs_trigger.rb

@@ -33,7 +33,7 @@ def default_attrs
           "focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2"
         ]
       }
-      base[:type] = :button if @as == :button
+      base[:type] = :button unless @as == :a
       base
     end
   end

gem/test/ruby_ui/tabs_trigger_test.rb

@@ -22,6 +22,13 @@ def test_renders_as_anchor_with_href_when_as_a
     refute_match(/type="button"/, output)
   end
 
+  def test_unexpected_as_value_still_renders_a_typed_button
+    output = phlex { RubyUI.TabsTrigger(value: "account", as: :buton) { "Account" } }
+
+    assert_match(/\A<button/, output)
+    assert_match(/type="button"/, output)
+  end
+
   def test_keeps_trigger_data_attributes_when_rendered_as_anchor
     output = phlex { RubyUI.TabsTrigger(value: "account", as: :a, href: "/account") { "Account" } }