Make HO information available in PFJet interface

Make HO energy+fraction available in the PFJet interface, pat::Jet, JetValidation, such that it becomes available at user level (in MiniAOD) given the importance of its understanding in Run II for high pT jets.
The actual PF algorithm that includes HO information into PF candidate reconstruction is not modified.
This request is mainly for user convenience.

Attached are plots from 10 events of the runTheMatrix workflow 13.0_QCD_Pt_3000_3500+QCD_Pt_3000_3500+DIGI+RECO+HARVEST.

pfclusterho_energy
![pfclusterho_energy](https://cloud.githubusercontent.com/assets/4518137/5043107/eabe0bae-6be1-11e4-859d-9b3f07182f54.png)
pfcandidate_rawhoenergy
![pfcandidate_rawhoenergy](https://cloud.githubusercontent.com/assets/4518137/5043108/ed3c2618-6be1-11e4-858a-4a13e1d1cac4.png)
pfjet_hoenergy
![pfjet_hoenergy](https://cloud.githubusercontent.com/assets/4518137/5043109/f034d0ae-6be1-11e4-81f4-c5b4afc80be4.png)
dqm_hoenergy
![dqm_hoenergy](https://cloud.githubusercontent.com/assets/4518137/5043111/f30ae462-6be1-11e4-91f5-c9b0f53955ab.png)
dqm_hoenergyfraction
![dqm_hoenergyfraction](https://cloud.githubusercontent.com/assets/4518137/5043113/f537b508-6be1-11e4-9d08-74a8a51da9ff.png)
HO energy is visible in these high energy jets, and this is visible in the PFjet, so technically it works.
this line alone increases the cost of reco::makeSpecific call by 50%
It's not a big deal here (it's not a very dense loop)
but some better use of the interface may be more adequate. The method interface already implies we are making PF object using PF inputs. A mix of typeid and reinterpret_cast may work faster (not sure if all needed manipulations will happen though)