Refactored GameBoard

Changed it from a static class to normal class, attempting to move
towards data coupling.
Deleted Board Control, moved update

Deleted Board Control and moved the update board function to GameBoard.
This was too get rid of static classes and moving towards data coupling,
getting rid of common coupling.
BoardData and GameBoard changed

Made BoardData a simmmple object and gave GamBoard an instance,
according to direct expressions Moving Fields To Objects.
Modified ComputerData

refactored ComputerData similair to BoardData,making it not static,
accepting and passing only what is necessary.
Switch Refactored

I extracted the validation and the altercation of the validateMove
method. The redundant validation check was placed into the
validateBoardAfterMove method check. This allows one method to perform a
single task and is easier to conceptualize versus the switch statement –
using the Cohesion principle. alterBoardState simply changes the current
boardState based on the validation. You will notice the use of the
Direct Expressions principle with the if/then/else statements and the
order in which they are arranged.
took out random init function

inits are bologne
BoardValidation...

It's f**ked up, needs further refactoring.