DayTwo refactor + CLI

[ramirez7]

• Refactored DayTwo to use an Either String to handle parse errors instead of the N* constructors.
  • I used Bifunctor, Traversable, and Applicative to process this either.
    • first from Bifunctor was used to augment the String error message with context.
    • traverse was used to process all the lines and short-circuit on first error
    • Applicative style (_ <$> _ <*> _) was used to process both sides of the round and pass them to the Round Vs constructor. LYAH has a good section on applicative style
• Reworked the types
  • Used fewer type synonyms (e.g. I think [Round] is preferable to Rounds)
  • Made Round a proper data type + used an infix Vs constructor. This just looks nice :)
  • Made a type for Win/Loss/Draw
• Wrote generally more point-free functions
  • I really like LambdaCase and used it quite a bit. It's a good syntax extension to learn!

---

I also made app/Main.hs an entrypoint for all the various days' mains. It parses the day number as the first argument, and then calls the correct day main with the rest of the args. Here's some example usage:

[armando@nixos:~/work/github/ola-advent-of-code-2022/haskell]$ cabal run haskell-exe -- 2 ./src/DayTwo/input.txt 
Up to date
12855

[armando@nixos:~/work/github/ola-advent-of-code-2022/haskell]$ cabal run haskell-exe -- 2 ./src/DayTwo/badinput.txt
Up to date
haskell-exe: Error in round 20 : Error parsing PlayOption: Prelude.read: no parse
CallStack (from HasCallStack):
  error, called at src/DayTwo/Solution.hs:76:58 in haskell-0.1.0.0-inplace:DayTwo.Solution

[armando@nixos:~/work/github/ola-advent-of-code-2022/haskell]$ cabal run haskell-exe -- 1 ./src/DayOne/input.txt 
Up to date
71934