Make TyphoonAssemblyActivator implicit

[jasperblues]

Rather than instantiating an activator like:

MiddleAgesAssembly *assembly = [MiddleAgesAssembly assembly];
[[TyphoonAssemblyActivator withAssemblies:@[assembly, anotherAssembly]] activate];

Then allow:

//This activates using the concrete collaborator classes specified in properties
MiddleAgesAssembly *assembly = [[MiddleAgesAssembly assembly] activate];

//This activates overriding a concrete collaborator class
MiddleAgesAssembly *assembly = [[MiddleAgesAssembly assembly] 
    activateWithCollaborators:@[anotherAssembly]];

• Allow overriding one or more collaborators, eg NetworkProvider with TestNetworkProvider
• Collaborators expressed as a protocol must be specified manually.

Rationale:

Don't especially want to change the API again, but benefits are:

• Tighter API
• Avoid confusion such as #Assembly property isn't filled with correct object in storyboard switch #337

Drawbacks:

Changes API again. . . Typhoon 3.1 feature?

[jasperblues]

Implemented. Intend to update docs and push as 3.1 - TyphoonAssemblyActivator is deprecated by this. One outstanding feature:

• When we inject an assembly we currently simply inject TyphoonComponentFactory. Its better to inject the activated assembly as properties of collaborators work correctly here.

Example:

//Inject TyphoonComponentFactory
@property ApplicationAssembly *assembly; 

assembly.modelProvider //Resolves to TyphoonCollaboratingAssemblyProxy

//Inject activated assembly
@property ApplicationAssembly *assembly; 

assembly.modelProvider //Resolves to activated ModelProvider