Integrate properties and classes from the auto extension to the main vocabulary

[mfhepp]

There are quite some properties (and some classes) that were originally "parked" in the auto extension module, but they are now regularily used on Web sites.

As the new Vehicle listings roll-out will lead to many more sites using auto-related markup, I suggest removing the confusion and integrating all or most of these elements to the core vocabulary.

Types (3)
BusOrCoach, Motorcycle, MotorizedBicycle

Properties (20)
accelerationTime, acrissCode, bodyType, emissionsCO2, engineDisplacement, enginePower, engineType, fuelCapacity, meetsEmissionStandard, modelDate, payload, roofLoad, seatingCapacity, speed, tongueWeight, torque, trailerWeight, vehicleSpecialUsage, weightTotal, wheelbase

Enumerations (1)
CarUsageType

Enumeration Members (3)
DrivingSchoolVehicleUsage, RentalVehicleUsage, TaxiVehicleUsage

[mfhepp]

Addendum:

1. Some, like bodyType are now even recommended properties in the Vehicle listings recipe.
2. Watch out for redundancies and renaming - e.g. seatingCapacity vs. vehicleSeatingCapacity.

This should be fixed before wide adoption will make things more difficult.

/CC @danbri @trypuz @sopekmir @MatthiasWiesmann

[mfhepp]

@danbri What will be the best way to get this done?