Add shadow support for registerReceiver with permission

Permission restriction has been added to registerReceiver / sendBroadcast.
Intents will only be broadcasted to receivers that has matching
permission. If null is provided then it will simply mean no permission
is required.

Posting the BroadcastReceiver on a provided Handler has also been
added.  If you provide a Handler when registering your receiver that
receiver will be notified from that Handler.  Otherwise the main
application Handler will be used.

Added necessary tests to exercise this new support.
Merge pull request #755 from lixar/feature/add-shadow-register-receiver-with-permission-support

Add shadow support for registerReceiver with permission
Change maven dependencies to compile against SDK 4.3_r1 (API 18).

Add Sergei to .pairs
Use version 4.3_r1 of android maven dependencies

These artifacts do not live on any public server (must build by hand and mavenize with new script)

 57 or so test failures but none of them are for obviously missing dependencies
Use @Implementation tag on shadow methods that are now part of the real classes
Ignore failing test. Intention of this test is unclear.

Particularly: whether the intent is to really delegate to Object or to the
Android code. In Robolectric 1.0 this meant not raising an Exception;
but in 2.0 this goes to View.toString(), which has a new implementation
thus failing the test.

There appears to be special handling of toString() in RL 2 code but we
don't understand enough to figure out if it's broken.
Run test with the right test runner, which inserts the right
ClassLoader, which loads the real Android code
Update TODO list in README
Update mavenize-android-new.sh to mavenize everything.

Also document how to build the Android JARs
- compiles against 4.3_r2
- Upgraded mavenize android script to use Android 4.3_r2
- Removed ShadowActivity#getWindowManger, which appeared to have no effect on anything
- ShadowContextImpl now special-cases construction of "window" system service, to create a WindowManagerImpl
- Shadow for internal class DisplayManagerGlobal
- Shadow for internal class WindowManagerGlobal
- pom.xml has (commented out) method for loading real android code at runtime
Invoke correct constructor (no-arg)
Pass real context
Shadow dalvik classes the "normal" way
ShadowLocaleData!
Fix RelativeLayoutTest to use fest assertions and fix failing test from upgrade.
Delete tests that had more to do with Application and Activity lifecycle than Settings
More tests that need a fully built & attached activity
Allow Robolectric to call through to the real libphonenumbers code

This required a custom step in our mavenization script for including the locale files into the android-ext jar file
Make the HTTP ParamParser considerably less ugly and increase test coverage.
Delete test for ShadowAnimatorSet, which was itself deleted a while ago