Android package name requires at least two segments
Fixes <uses-sdk> tag appears after <application> tag
Ignore lint warnings for unregistered activities

This fixes the tons of irrelevant warnings about the activities in tests
not being registered.
Base native fragment classes added
Fragment Injection error checking.
Preliminary Fragment refactoring
Revert "Android package name requires at least two segments"

This reverts commit e0e9c2f48ff3080b44ec695822860d5ebe7f0326.
Fixed silly error when injecting views
Added native fragment bindings in default module

I've also used fully qualified names for Fragment in classes where both
the support library and native fragments are used - it makes things less
confusing.
Hacks to manage classloading.

All tests now pass. I haven't added any new tests though, so that should
be done before any merging.
DRY-ing out some duplicate code
Removed useless code and leftover debug statement

The pattern of
```java
@Override protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
}
```
is done to allow testing of methods outside the package of the test
class. Robolectric 2.0 adds convenience methods for this, so consider
this the start of the cleanup. None of these are actually called in the
tests.
Arranged new classes in better package structure.
Added tests

I modified RobolectricRoboTestRunner to properly handle situations where
the support library or native fragments aren't available.
Added generic type arguments/suppressed warnings

Improved type safety and reduced the number of yellow squiggly lines in
the project.
Deprecated the subclasses of deprecated classes
Scaffold for native fragment injection tests.

For the life of me I can't figure out how to get Robolectric working
with this class, or the standard activity tests. It works on a real
device though, the fields get injected properly.
New merge attempt
--amend
--amend