USB PID fixes

Many boards were using the Revolution PID.
* FlyingF3, DiscoveryF4, FlyingF4 are all now mapped to a "spare" PID.  These boards need to either get their own PID or else we need to just map all TauLabs boards onto a single PID.
* Freedom is now using the proper PID registered by @peabody124.

I dropped the redundant USB board IDs that were being OR'ed into the bcdDevice field in the USB descriptor.  Nothing used these IDs and they didn't match the authoritative ones in the board-info.mk files.

The Windows .inf file didn't have entries for FlyingF3, DiscoveryF4, FlyingF4, Freedom or Quanton.  Now it does.  @lilvinz how was Quanton working on windows without this now that the new USB CDC descriptors are in place?

The Windows .inf file is now renamed to TauLabs-CDC.inf.  Docs should be updated.

The missing entries in the .inf file were causing issues on win7 + DiscoveryF4 for a user named "john____" on IRC.  He tested the new entry and it fixed his issue.