feat(android): activity result use new API and updated permission result callbacks to match

[carlpoole]

• Removes the need to define request codes on plugins. requestCodes element removed from @CapacitorPlugin annotation (breaking change for plugins with activity results on Capacitor 3 beta)
• Activity result callbacks are registered by adding the @ActivityCallback annotation to a method with the parameters (PluginCall, ActivityResult).
• Permission result callbacks are registered by adding the @PermissionCallback annotation to a method with the parameter (PluginCall)
• The permissionCallback element is removed from the @PluginMethod annotation (breaking change for plugins with permission requests on Capacitor 3 beta)
• Activities are launched using the new method startActivityForResult(PluginCal call, Intent intent, String callbackName); and link to the registered callback by providing the name of the callback method.
• Existing permission request methods were modified to add the callback method name parameter, for example requestPermissionForAlias(String alias, PluginCall call, String callbackName);

Resolves #4050

[jcesarmobile]

I've been doing some testing on the sample app and on camera page the app crash on the second time I click the "Request all permissions" button (or with the photo permissions too) because of null savedCall on triggerPermissionCallback method.
I tried to put a null check and that only avoids the crash, then one of each call works and the following doesn't because it's null, then the following works again and so on, so loos like the bridge.getPermissionCall(handle.getId()); is not working properly or it's not getting stored properly

[carlpoole]

I've been doing some testing on the sample app and on camera page the app crash on the second time I click the "Request all permissions" button (or with the photo permissions too) because of null savedCall on triggerPermissionCallback method.

Nice catch. Thanks for testing, the call was being saved twice so subsequent permissions checks on the same plugin were trying to find an old call and fetching null instead.