Add missing InlineData for numeric UInt64.MaxValue test case

The base class has two test cases for UInt64.MaxValue:
1. EnumU64.Max (symbolic enum value)
2. (EnumU64)18446744073709551615 (numeric literal)

Added the missing InlineData attribute for the numeric literal case. Both test cases now properly handle MariaDB's different serialization format through the runtime adjustment logic.

Test behavior on MariaDB 10.6+:
- EnumU64.Max test case: Adjusts expectation from {"Prop":-1} to {"Prop":18446744073709551615}
- (EnumU64)18446744073709551615 test case: Already expects {"Prop":18446744073709551615}

All 7 test cases now pass on both MySQL and MariaDB.

Co-authored-by: renemadsen <[email protected]>

Author: Copilot

test/EFCore.MySql.FunctionalTests/Query/JsonTypesRelationalMySqlTest.cs

@@ -61,6 +61,7 @@ public override Task Can_read_write_collection_of_ulong_enum_JSON_values()
         [InlineData(EnumU64.Default, """{"Prop":0}""")]
         [InlineData(EnumU64.One, """{"Prop":1}""")]
         [InlineData((EnumU64)8, """{"Prop":8}""")]
+        [InlineData((EnumU64)18446744073709551615, """{"Prop":18446744073709551615}""")]  // Additional test case for UInt64.MaxValue as numeric
         public new async Task Can_read_write_ulong_enum_JSON_values(EnumU64 value, string json)
         {
             // MariaDB serializes UInt64.MaxValue as "18446744073709551615" instead of "-1"