model: Slight modification with wire format processing

Now it is possible to convert Name from/to wire format via ndn::Face
helper method (since Face is getting configured with specific wire
format)

Refs #1008 (http://redmine.named-data.net/issues/1008)
model: Updated API for pluggable wire format

As of this commit, the selected (default) wire format is controlled via
global variable ndn::WireFormat:

    Config::SetGlobal ("ndn::WireFormat", IntegerValue (ndn::Wire::WIRE_FORMAT_CCNB));

or

    ./waf --run="... --ndn::WireFormat=1

Refs #1008 (http://redmine.named-data.net/issues/1008)
model: Another major change: switching to NDN.cxx API for ndn::Name

NDN.cxx code is almost exactly the same, with minor NS-3 specific customizations

Refs #1011 (http://redmine.named-data.net/issues/1011)
model: Bug fixes and small API change in ndn.cxx

ndn.cxx API need to be back-ported back, since it has important and not
very obvious problem.

Refs #1011 (http://redmine.named-data.net/issues/1011)
model: A couple of tricks and fixes in NDN.cxx, so it will play nice with python bindings

Refs #1011 (http://redmine.named-data.net/issues/1011)
PyNDN: Initial import of PyNDN code

Refs #1010 (http://redmine.named-data.net/issues/1010)
PyNDN: Initial changes of PyNDN emulation in ndnSIM

The biggest problem so far, which I cannot solve at all, is exception
handling.  NDN.cxx throws many exceptions when something bad happens,
with are not handled by python bindings

Refs #1008 (http://redmine.named-data.net/issues/1008)
Refs #1011 (http://redmine.named-data.net/issues/1011)
PyNDN: Simplified versions of Interset and Name are now seem to be fully working

Refs #1010 (http://redmine.named-data.net/issues/1010)
model: Add ability to print interest to the standard output, so it plays nice with PyNDN

Refs #1010 (http://redmine.named-data.net/issues/1010)
PyNDN: Finishing basic implementation of PyNDN emulation

Not yet fully tested

Refs #1010 (http://redmine.named-data.net/issues/1010)
PyNDN: Small change and installing API

Refs #1010 (http://redmine.named-data.net/issues/1010)
model: Enabling serialization/deserialization of Exclude filter in ndnSIM wire format

Refs #1009 (http://redmine.named-data.net/issues/1009)
model: Adding exclude filter processing in all content store implementations

Although exclude filter is honored now by content stores, forwarding
strategy is completely ignoring them.  That is, if somebody replies to
an interest with a data packet that violates the filter, this data
packet will propagate back to the requester.  This "problem" may or may
not be addressed in future.

Refs #1009 (http://redmine.named-data.net/issues/1009)