Implement the initial classes and objects for player controlled vehicles

[soulerlunar]

Now having design documentation for the vehicle classes, the next step in development is to start implementing the actual code for these. We will make the first proper modifications to the code repository for the game.

We will create a new branch in which we will develop this code so that it can be used for development. We then implement each of the classes and use this as a chance to get to know classes/objects in Unity. We will then figure out how to test it—ideally we should figure out tests before implementation, but that's a goal to aspire to for future dev cycles.

We will finally determine if the code we have put together is ready to be merged into dev or if we'd rather wait a little bit and leave it on its branch for future development.

[soulerlunar]

I have created the branch we will be using here.

[Repsaj11]

We have changed the name and goal of this issue because we realized that we cannot implement everything relating to this issue, so we will create later issues to implement the parts that are no longer covered by this issue.

[soulerlunar]

Today we started work on creating the scripts for the code. We have created empty scripts for Vehicle, VehicleEntity, PlayerVehicleEntity, and NPCVehicleEntity. Each now has their variables declared and the defined functions in the design docs declared but not written yet. We also created a prefab for Vehicle, though for now it is just a cube.

The next step we need to do is find a temporary model to use as a default "vehicle" so that we can use it in testing driving around. We will then also write the movement based methods for VehicleEntity and then discuss with the rest of the team the idea of necessary buttons that will be used for movement in the game. We will then use the buttons as base keybinds for the PlayerVehicleEntity's controlling script. This should allow us to have a testable vehicle to drive around.