Android actions fixes #1

[SergChr]

Fixes

• Changed IntentClass => IntentClassName.
• Added ability to send android_actions as an array, for example:

{
 "to" : "fcm_token",
 "data" : {
     "custom_notification": {
     	  "android_actions": ["First action", "Second action"],
	      "color":"#00ACD4",
	      "priority":"max"
    }
 }
}

• As android_actions is an ArrayList so the bundle can't correctly be parsed, I have added bundle.remove("android_actions"); to avoid any parsing errors (we will not use this field further so it is unnecessary). Any workarounds for this or it's OK?

[evollu]

let's keep the bundle as is

[SergChr]

@evollu okay, so what the way to keep android_actions and don't come across parsing error? It happened when parsing the Intent in FIRMessagingModule.java: it can't parse ArrayList.

[evollu]

hmm..ok

[evollu]

Intent actionIntent = new Intent(mContext, intentClass); is still failing

[SergChr]

@evollu in this PR it was changed to

Intent actionIntent = new Intent();
actionIntent.setClassName(mContext, intentClassName);

thus it shouldn't failing

[evollu]

I've published the change.
The field is changed to take a JSON string config.

[SergChr]

@evollu thanks