Adding a Blacklist registry to API

This was just a thought that I had, and I discussed with @NeverCast, he thought it sounded good, however has I wasn't completely sure I thought I'd PR it instead of push it.

Basically this adds the ability for other mods to register classes to us that they don't want us to allow the computer to interact with. It also has the added bonus for us where we can remove certain things that the computer handles that it shouldn't as it has no methods other than ```listMethods```, a fantastic example being the Enchantment Table.

I've added some items from Vanilla and Thaumcraft that I knew for sure didn't need to be wrapped, I also added the ```IPeripheral``` to the list as well, just as initial examples, I'm sure we could find more that really don't need to be in.

The API also defines a list of classes that can never be added to the blacklist as it may break things, such as ```TileEntity```

Known Bug:
— This one is an existing bug, and this solution did not fix it (nor was it intended to); Command Blocks return null from us, but ComputerCraft doesn't handle them unless it's directly attached to the computer, instead of via network cables. Similar report was made on issue #61

Hopefully you can see what I've done here and see the merit and uses for it, but let me know what you think, both for us and mods that use our API.