work around annoying core bug where starting a timer of 0 uses self.t…

…imer instead. But that annoying bug has to stay since over a decade worth of mods has assumed that to be valid

DBM-Raids-BfA/EternalPalace/LadyPriscillaAshvane.lua

@@ -70,7 +70,7 @@ mod.vb.shieldDown = false
 mod.vb.blueone, mod.vb.bluetwo = nil, nil
 mod.vb.redone, mod.vb.redtwo = nil, nil
 mod.vb.greenone, mod.vb.greentwo = nil, nil
-local easyUpSurgeTimers = {0, 16, 37.9, 16.5, 16, 24}
+local easyUpSurgeTimers = {0.000001, 16, 37.9, 16.5, 16, 24}
 
 local updateInfoFrame
 do

DBM-Raids-BfA/EternalPalace/QueenAzshara.lua

@@ -199,10 +199,10 @@ local HulkTimers = {
 	["Mythic"] = {35, 65},
 }
 local phase4LFROverloadTimers = {14, 69.8, 75, 65, 65, 60}
-local phase4LFRPiercingTimers = {0, 65, 65, 65, 60, 20}
-local phase4LFRBeckonTimers = {0, 90, 100, 80}--LFR and Normal (so far, greater data might find divergence)
+local phase4LFRPiercingTimers = {0.000001, 65, 65, 65, 60, 20}
+local phase4LFRBeckonTimers = {0.000001, 90, 100, 80}--LFR and Normal (so far, greater data might find divergence)
 
-local phase4NormalPiercingTimers = {0, 65, 65, 65, 55, 20}--Not same as LFR, one is different
+local phase4NormalPiercingTimers = {0.000001, 65, 65, 65, 55, 20}--Not same as LFR, one is different
 local phase4NormalPortalTimers = {35, 34.9, 87.5, 32.4}
 
 local phase4HeroicOverloadTimers = {14, 44.9, 44.9, 45, 40, 40, 40}

DBM-Raids-BfA/Nyalotha/NZothTheCorruptor.lua

@@ -278,7 +278,7 @@ local allTimers = {
 	["mythic"] = {
 		[1] = {--Unique to Mythic
 			--Basher tentacles
-			[318714] = {0, 35, 35, 50, 35},
+			[318714] = {0.000001, 35, 35, 50, 35},
 			--Paranoia
 			[315927] = {15, 85.1},
 			--Eternal Torment