Include known range for learned moves & display definitely known moves

Run the other day had an instance where gym leader had the same mon as the player. Player ended up speeding through looking at the tracked moves & forgot for a moment they were the last moves the player mon had learned, not the ones you'd see at there level.

The three main changes intended:

When learning a move, mark the level it is learned as the low, and the last level we know it'll be had as the high (this is just from looking at the learn levels and looking 4 moves ahead)
When inspecting an opposing mon, make sure moves that the player would know it will have are listed first -- we know it will have the move if minLv is below / equal to it and maxLv is above / equal to it, as any two of the same mon at the same level will have the same move.
When a move is not guaranteed to be had by the given mon, mark it with an asterisk so the player knows to try and confirm more details in the move history window.

There's definitely some clean up I listed inline, just making a pr to point to as a reference for discord :)

Handling for mons that learn 2 moves at the same level (could hack this sort of thing in but figured easier to just leave in case there was an obvious approach to it)
just made a quick concat for the * next to 'not sure if known moves', would want to match the blue color probably
Could be considered to be doing too much calc for the player: could either add a flag on the tracked move that it was learned on a level up / can exclude from list of moves, or recalculate from the levels, to narrow down displayed moves a bit more when you know the move isn't learned until later
need to update move button https://github.com/besteon/Ironmon-Tracker/blob/dev/ironmon_tracker/Input.lua#L261, probably better approach is to move most of the datahelper changes to tracker.getMoves & have that take an optional parameter of level.

Couple quick screenshots of what this does after:

catching level 3 hariyama
leveling to 19
returning and seeing a level 3 in grass

Zac pointed out https://github.com/besteon/Ironmon-Tracker/issues/202, so for reference what this would display for the mons mentioned in that issue:

Forretress after step 3

assuming only the moves described, so the move history showing:

ember min 8 max 8 steel wing min 3 max 5 psychic min 3 max 5 fire punch min 3 max 5 dream eater min 3 max 5 (the first move seen, as shown in screenshot as it's the one not listed)

lvl 3-5 show

dream eater / steel wing / psychic / fire punch confirmed

lvl 6-7 shows

ember / fire punch / steel wing / psychic same as now, except marked with * on each

lvl 8 shows

ember as confirmed
fire punch, steel wing, psychic marked with * on each

lvl 9+ shows

ember, fire punch, steel wing, psychic mark marked with * on each

krabby

https://github.com/besteon/Ironmon-Tracker/issues/202#issuecomment-1359200969 I'm assuming move order is that they were seen top to bottom to illustrate, but it only swaps out what the *'d ones will be, which would show in the same priority order as they do now

lvl 3-7

outrage confirmed
synthesis, grudge, aeroblast have *

lvl 8

outrage, hydro pump confirmed
synthesis, grudge *

lvl 11

charm confirmed
synthesis, grudge, aeroblast have *

lv 15-17

spark confirmed
synthesis, grudge, aeroblast have *

lv 21-22

return confirmed
synthesis, grudge, aeroblast have *

lvl 27

aeroblast and baton pass confirmed
synthesis, grudge have *

lv 30

synthesis, grudge confirmed
aeroblast, baton pass have *

all other levels get same as now except * on moves (besides whatever is on page 2)

Altaria

https://github.com/besteon/Ironmon-Tracker/issues/202#issuecomment-1363686571

lvl 27

pursuit, kinesis, magic coat, extrasensory all confirmed

lvl 28-31

kinesis, magic coat confirmed
extrasensory, pursuit marked with *

lvl 32-33

sandstorm, egg bomb, kinesis, magic coat all confirmed

all other levels get current behavior

One other minor improvement I could see including would be to use level ranges for simple cases as well -- that is, since an altaria learns moves at 11 and 18, we know that seeing a move at 11 means it will have it until 17 at least. This would make it so e.g. we'd also know all the moves for sure when seeing a level 34 altaria in the example above.

In theory we could calc out even more for altaria, but that would be a mistake both for code complexity reasons & doing the work for the player -- just give them the obvious ones and indicate they should treat the others with suspicion / investigate move history to see what they can figure out

besteon / Ironmon-Tracker