Skip process interface

Hi David,
The more I thought about it the more I disliked the python InputTag interface I suggested for handling skip current process handling. What one uses in python would be different in how it would be done in C++. Also, the fact that if a user gave us both a process name and set the 'skipCurrentProcess' argument to True meant we could get an inconsistency bothered me. Therefore I changed to code so that is is purely based on process name which a user can get by calling a static function of cms.InputTag. However, using 'skipCurrentProcessing' as the name 'conflicted' with the same function on the C++ InputTag side which does a different task. So on C++ I switched the function name to  'willSkipCurrentProcess' since I felt 'skipCurrentProcess' could be misinterpreted as setting the InputTag to do that action rather than asking if the InputTag was going to do a skip.
I'm making this a pull request rather than doing a CVS commit so that I don't break any other code you might be working on.