LocalActivityInvoker#getActivityResult() should wait for Activity with timeout

### Description

LocalActivityInvoker#getActivityResult() throws exception immediately if Activity is not finished when this method is invoked, while InstrumentationActivityInvoker#getActivityResult() waits for Activity to be finished with a timeout duration of ActivityLifecycleTimeout.

This behavior was by design as Robolectric test is usually run in a single thread. However, there is a use case where a test has two threads and one thread is computing an expensive operation while the test main thread is waiting.

To reduce the behavior difference between Local and Device test, LocalActivityInvoker#getActivityResult() should wait for Activity with timeout.

Start with LocalActivityInvoker#getActivityResult() and compare its behavior with InstrumentationActivityInvoker#getActivityResult(), using ActivityLifecycleTimeout as the timeout reference. The change is complete when the local invoker waits for the Activity result up to the timeout instead of failing immediately, while preserving the documented behavior for tests.

Written by the indexing model from the issue text.