added startActivity function

Related to appium/appium #2969.  Added startActivity api that maps to new appium feature.
In that case, we can't have overloads to handle all the cases. That's why I
went with the map.  We can have:

startAct(appPkg, appAct)
startAct(appPkg, appAct, appWaitPkg OR -Act) <= can't have overloads for
both cases, won't compile
startAct(appPkg, appAct, appWaitPkg, appWaitAct)

I say we either just go for signature #3, in which case users will have to
pass null for whichever of the last 2 they don't care about, or we stick
with the hash map.

On Saturday, September 6, 2014, Jonathan Lipps <notifications@github.com>
wrote:

> In src/main/java/io/appium/java_client/AppiumDriver.java:
>
> > @@ -168,6 +169,17 @@ public String currentActivity() {
> >      Response response = execute(CURRENT_ACTIVITY);
> >      return response.getValue().toString();
> >    }
> > +
> > +  /**
> > +   * Launches an arbitrary activity during a test. If the activity belongs to
> > +   * another application, that application is started and the activity is opened.
> > +   * This is an Android only method.
> > +   * @param options 'appPackage' and 'appActivity' are required;
> > +   *                'appWaitPackage' and 'appWaitActivity' are optional
> > +   */
> > +  public void startActivity(Map<String, String> options){
>
> Yes, you can have just one of them.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/appium/java-client/pull/101/files#r17211060>.
>