Computer player prediction and debugging changes
Computer player prediction and debugging changes

- The computer player now has a method `predict_intercept` that takes
  the ball's current position and vector and attempts to calculate the
  y-intercept with the player's paddle's range of motion.

- In the course of implementing this, I discovered that my computer
  paddle looked like it was performing okay when eyeballing the path
  of the ball but that it was moving a lot up until the last
  second. This implies that its earlier calculations were very wrong.

- Due to frustration with these errors, I added code that prints out
  the path the computer player estimates the ball will follow. This
  sent me down a 3 hour trig hole. I am not a smart man.

chuckSMASH/pong