Break down Porygon.go with separate packages for readability

[arniethepie]

Description

I had a go at splitting up the 700 line Porygon.go file into different packages. Not a Go expert so these probably could have been separated a little bit better. Also low hanging fruit but changed deprecated ioutil just to io.

Packages created:

• Porygon/config
  • For config struct and config parsing.
• Porygon/database
  • For db connection and db queries. I didn't really refactor this, I just split it up into different methods in the package that would slot in place in the go func in main.go. Definitely needs improvement because I wasn't sure how to expose the config to this package so you have to pass the config into every query function 💀
• Porygon/discord
  • For constructing the embed message field for discord, haven't moved any of the discord functionality from main.go into here tho because I wanted a better way to do it)
• Porygon/pokemon
  • This is mainly for the Pokemon, Raid, Incident structs to keep main.go a bit cleaner, i also dumped FormatEmoji in here but it can definitely go somewhere better
• Porygon/query
  • This is just for the query made to the Golbat API (?) , can be extended for more queries if wanted I'm sure but for now just wanted the API request functionality out of main.go (though I didn't move the actual core usage of query.ApiRequest out of main.go. Also the name maybe a little confusing, wanted to name it golbat or maybe external (similar usage in the Golbat repo I think)
• renamed Porygon.go to main.go
  • Sorry I think main.go is better

As for testing, running Porygon for the past few hours has been fine with these changes, no errors. Functionality is exactly the same. As for adding actual tests, probably a future thing :P.

Still a lot of work to be done in terms of refactoring but hopefully this is just a starting.

[roundaboutluke]

nit picky, but my only criticism is the naming of query.go and stats.go - both technically provide stats, and both are technically queries :D something like api.go and db.go might be more fitting just to further improve readability? :)

[arniethepie]

nit picky, but my only criticism is the naming of query.go and stats.go - both technically provide stats, and both are technically queries :D something like api.go and db.go might be more fitting just to further improve readability? :)

Agreeeeeeed, merged

[roundaboutluke]

@AppIe314 approved, thanks again!