Fix clippy warnings for ARM64 FJCVTZS implementation

Co-authored-by: sapphi-red <49056869+sapphi-red@users.noreply.github.com>

Author: Copilot

crates/oxc_ecmascript/src/to_int_32.rs

@@ -8,7 +8,6 @@ pub trait ToInt32 {
 }
 
 impl ToInt32 for f64 {
-    #[expect(clippy::float_cmp, clippy::cast_possible_truncation, clippy::cast_possible_wrap)]
     fn to_int_32(&self) -> i32 {
         #[cfg(target_arch = "aarch64")]
         {
@@ -43,6 +42,7 @@ fn f64_to_int32_arm64(number: f64) -> i32 {
 
 /// Generic implementation of ToInt32 for non-ARM64 architectures
 #[cfg(not(target_arch = "aarch64"))]
+#[expect(clippy::float_cmp, clippy::cast_possible_truncation, clippy::cast_possible_wrap)]
 fn f64_to_int32_generic(number: f64) -> i32 {
     const SIGN_MASK: u64 = 0x8000_0000_0000_0000;
     const EXPONENT_MASK: u64 = 0x7FF0_0000_0000_0000;
@@ -118,6 +118,7 @@ pub trait ToUint32 {
 }
 
 impl ToUint32 for f64 {
+    #[expect(clippy::cast_sign_loss)]
     fn to_uint_32(&self) -> u32 {
         self.to_int_32() as u32
     }
@@ -128,6 +129,7 @@ mod test {
     use super::*;
 
     #[test]
+    #[expect(clippy::cast_precision_loss)]
     fn f64_to_int32_conversion() {
         assert_eq!(0.0_f64.to_int_32(), 0);
         assert_eq!((-0.0_f64).to_int_32(), 0);