dbop_sqlite: avoid use of UNIXEPOCH for allocated_eids

UNIXEPOCH is only supported by sqlite 3.38+.
Leap 15.3/15.4/15.5/15.6 has 3.44, but AlmaLinux 9 has
a lackluster version 3.34.1.

Since the allocated_time is not really used for anything,
we can just put 0 there.

References: DESK-2748, DESK-2754
Fixes: gromox-2.35-33-g2cab2c5a1

Author: jengelh

lib/dbop_sqlite.cpp

@@ -338,7 +338,7 @@ static constexpr char tbl_replguidmap_14[] =
 static constexpr char tbl_fixsyseidalloc_15[] =
 "INSERT INTO allocated_eids (range_begin,range_end,allocate_time,is_system) "
 "VALUES ((SELECT MAX(range_end)+1 FROM allocated_eids), "
-"(SELECT MAX(range_end)+0x10000 FROM allocated_eids),UNIXEPOCH(),1)";
+"(SELECT MAX(range_end)+0x10000 FROM allocated_eids),0,1)";
 
 static constexpr char tbl_fixsyseidalloc_16[] =
 "UPDATE configurations SET config_value=(SELECT MAX(range_begin) FROM allocated_eids) WHERE config_id=2"; // CONIFG_ID_CURRENT_EID