Fix max_execution_time being set to 30 and not 0

This was a regression introduced in
76dcd3f.
Changing the loose == operators to strict ===
caused behavior to change. max_execution_time got
set to 30 instead of 0 as intended.

Fix by calling intval() so that the ===
comparisons work.

Author: john-shaffer

CHANGELOG.md

@@ -1,5 +1,7 @@
 ## Unreleased
 
+- Fix max_execution_time being set to 30 instead of 0.
+
 ## Static Deploy 9.0.0 (2025-07-16)
 
 This is the first release under the name Static Deploy.

src/Utils.php

@@ -58,11 +58,11 @@ public static function set_max_execution_time(): void {
             return;
         }
 
-        $current_max_execution_time  = ini_get( 'max_execution_time' );
+        $current_max_execution_time  = intval( ini_get( 'max_execution_time' ) );
         $proposed_max_execution_time =
             ( $current_max_execution_time === 30 ) ? 31 : 30;
         set_time_limit( $proposed_max_execution_time );
-        $current_max_execution_time = ini_get( 'max_execution_time' );
+        $current_max_execution_time = intval( ini_get( 'max_execution_time' ) );
 
         if ( $proposed_max_execution_time === $current_max_execution_time ) {
             set_time_limit( 0 );