Document a bunch of info tables (based on comments mainly)

[Feacur]

general reasoning:

• it's easier to see actual constants than read comments
• comments were only in one place, but constants are ubiqutous
  • (some comments are preserved, though; did't want to inflate names)

concerning the dialogues with Gorons @ z_en_go.c:

• these inf table flags are used to not repeat certain messages
• so, the main purpose of new name is to convey the fact that they've said something already
• definitely, naming can be improved
  • say, Ingo offers Link a ride after they've met for the first time

    in that case `INFTABLE_9A` for message `0x2030` "do you want to ride one of my fine horses?"
    might be be something like `INFTABLE_TALKED_TO_INGO_FIRST_TIME`, like it was done for Malon
    

  • but sometimes it's a bit of a hassle

    the purpose of `INFTABLE_10F` for messages
    - `0x3041` "Dad and you destroyed the dragon together, didn't you!"
    - `0x3042` "When I grow up, I want to be a strong man like you"
    is to eliminate repeated opening lines. all's good, but `INFTABLE_TALKED_TO_GORON_FIRST_TIME`
    would be a bad name, because the actor profile is shared between entities. i need to find a
    unique name for each of the cases rather than resort to "the-one-over-there-before-an-event"
    these info is better placed as comments so that LSP would tell you any extended meaning
    
    meanwhile `INFTABLE_TALKED_TO_GORON_MSG_3041` or `INFTABLE_HEARD_MSG_3041` should do, i think
    
    `INFTABLE_EB` might be `INFTABLE_KNOW_ABOUT_BOMB_FLOWERS`, but it can be done later, given the
    change makes a difference
    

one way or another will conflict a bit with #2299 at some info tables. negligible, just for me to keep in mind