Support for Start() method that fires after constructor but before the first Update()

[ticking-clock]

Adds an optional overridable Start() method on TestableComponent that will be called after the constructor but before the first Update(). Included a test for verification.

The purpose of this is to allow authors to write Component classes that feel more like they inherited from MonoBehaviour. It is also sometimes desirable to guarantee that code executes after Awake() (which in this case is simulated by the constructor).

I'd like to add support for Awake() but can't see a viable way to do it with injection (Awake must be called after all objects are initialized).

[banderous]

Why is this necessary? All you need to do is direct the Start() method of UnityGameObjectBridge through TestableGameObject, which you've already done.

[ticking-clock]

You're right; not only does this not belong here but results in Start() being called twice in Unity. I was trying to support the Start() method in tests since they don't instantiate UnityGameObjectBridge, but now I think that logic should go in Tests.TestUpdatableManager.

[ticking-clock]

Fixed per banderous's comment and merged into single commit.