Organize ALL the launch files

[dSaucePercussion]

We want to organize our launch files to make it easier to find the correct files when we're running simulations and when we are running the real robot.

Primary Goals
In the cr17 package, there should be two primary launch files:

• There should be a launch file that runs all of our nodes
• There should be a launch file to run the entire physical robot, including sensors and the launch file that launches all of our nodes (the above item)

In the simulation_2017 package, there should be one primary launch file:

• There should be a launch file that includes the launch file that launches all of our nodes and includes necessary simulation sensors

Secondary Goal

• After these primary goals are met, we can make some launch files particular to certain nodes, nesting them hierarchically.

[JacobAMason]

@bgrayd @nathantfrank @dSaucePercussion @RogerSGarcia I got rid of a majority of the launch files in the simulation package. Teleop is in control_teleop.launch and Autonomous (old hlsm.launch) is in control_autonomous.launch.

Both sims are using the new robot model that @bgrayd made.

The Autonomous sim (hlsm) doesn't appear to do anything, but the teleop sim works, so I imagine it won't be difficult to get the autonomous sim working with the new robot model.

[JacobAMason]

Amended my commit because I realized it didn't grab all my changes. Not sure what I did wrong, but now it should be usable.