core, frontends, bridgen plugins: fixed methods which were unproperly managing multi-profiles

- added profile argument to askConfirmation, actionResult, actionResultExt, entityDataUpdated, confirmationAnswer, getProgress
    - core, frontends: fixed calls/signals according to new bridge API
    - user of proper profile namespace for progression indicators and dialogs
    - memory: getParam* now return bool when param type is bool
    - memory: added getStringParam* to return string instead of typed value
    - core, memory, storage, quick_frontend: getHistory now manage properly multi-profiles
    - plugins XEP-0047, XEP-0054, XEP-0065, XEP-0077, XEP-0096; multi-profiles proper handling

src/bridge/bridge_constructor/bridge_template.ini

@@ -106,18 +106,19 @@ doc_param_1=%(doc_profile)s
 [askConfirmation]
 type=signal
 category=core
-sig_in=ssa{ss}
+sig_in=ssa{ss}s
 doc=A confirmation is needed for an action
 doc_param_0=conf_type: Type of the confirmation, can be:
  - YES/NO: A question which need a yes or no answer
  - FILE_TRANSFER: A confirmation is needed before transfering a file
 doc_param_1=id: Id of the confirmation query
 doc_param_2=data: conf_type dependent data
+doc_param_3=%(doc_profile)s
 
 [actionResult]
 type=signal
 category=core
-sig_in=ssa{ss}
+sig_in=ssa{ss}s
 doc=Requested result of an action
 doc_param_0=answer_type: Type of the answer, can be:
  - SUPPRESS: The action is managed, the id MUST be removed from queue
@@ -126,16 +127,18 @@ doc_param_0=answer_type: Type of the answer, can be:
  - RESULT: General result, interpretation depend of the action
 doc_param_1=id: Id of the action
 doc_param_2=data: answer_type specific data
+doc_param_3=%(doc_profile)s
 
 [actionResultExt]
 type=signal
 category=core
-sig_in=ssa{sa{ss}}
+sig_in=ssa{sa{ss}}s
 doc=Requested result of an action (Extended)
 doc_param_0=answer_type: Same as for [actionResult] but with the following additional one:
  - DICT_DICT: As RESULT, but returned as a dictionary of dictionary 
 doc_param_1=id: Id of the action
 doc_param_2=data: answer_type specific data
+doc_param_3=%(doc_profile)s
 
 [entityDataUpdated]
 type=signal
@@ -462,14 +465,16 @@ doc_return=list of categories
 async=
 type=method
 category=core
-sig_in=ssib
+sig_in=ssibs
 sig_out=a(dssss)
 param_3_default=True
+param_4_default="@NONE@"
 doc=Get history of a communication between two entities
 doc_param_0=from_jid: source JID (bare jid for catch all, full jid else)
 doc_param_1=to_jid: dest JID (bare jid for catch all, full jid else)
 doc_param_2=limit: max number of history elements to get (0 for the whole history)
 doc_param_3=between: True if we want history between the two jids (in both direction), False if we only want messages from from_jid to to_jid
+doc_param_4=%(doc_profile)s
 doc_return=Ordered list (by timestamp) of tuples (timestamp, full from_jid, full to_jid, message, type)
 
 [addContact]
@@ -519,20 +524,22 @@ doc_param_2=%(doc_profile_key)s
 [confirmationAnswer]
 type=method
 category=core
-sig_in=sba{ss}
+sig_in=sba{ss}s
 sig_out=
 doc=Give answer to a confirmation request
 doc_param_0=id: id of the confirmation request
 doc_param_1=accepted: True if the action is confirmed
 doc_param_2=data: action specific data
+doc_param_3=%(doc_profile)s
 
 [getProgress]
 type=method
 category=core
-sig_in=s
+sig_in=ss
 sig_out=a{ss}
 doc=Get progress information for an action
 doc_param_0=id: id of the progression status
+doc_param_1=%(doc_profile)s
 doc_return=dict with progress information:
  - position: current position
  - size: end position