Fixed default_account_changed callback not triggered when default account is deleted + added account removed callback (and renamed account created callback)

This reverts commit 0bf65d31.

- Do not use temporary variable in soci:use

Conference Scheduler:
- Do not attempt to send an ICS message to ourselves

Capability Negotiation Tester:
- When a call changes encryption towards DTLS or ZRTP, wait for the callback encryption change before moving on as ZRTP key negotiation might be slow in some cases

Local Conference Tester:
- Expand usage of wait_for_conference_streams to make sure that a conference is full established instead of relying on the number of the state changes of a call to a particular state

Tester:
- Update suite expected duration

Add X-Linphone-Provisioning custom header to http requests for remote provisionning. Improve documentation.

sure to get accurate volumes

database: when selecting a conference info, check that the ordered uri
string is the same as the one stored in the database. If it is not the
case, update the database entry to avoid issues when searching the
conference information by its address

is destroyed.
Fix return value of Account::customContactChanged when two addresses are
compared

johan authored 1 year ago and johan committed 1 year ago

+ SRTP AES128-GCM is the default mode

- For backward compatibility, never set local and peer addresses of the ConferenceID object to nullptr
- Clean up temporary database tables before starting an update because
they are not deleted if the MainDb::updateSchema() fails
- Reply 481 Transaction Does Not Exist to any INVITE or UPDATE received
after the BYE is sent

Add new video codec priority policy, that gives preference to hardware codecs on mobile platforms, in order to preserve battery and improve framerate.

Make ChatMessagePrivate::setState private because the chat message state
can only be set by ChatMessagePrivate::setParticipantState if has to be
changed from outside of the ChatMessage object

   Set it as Address in account parameters and core in order to easily
   take advantage of address comparison, parameter management and
   compliance with RFC3261

Conference:
  Allow applications to directly mute licrophone and get input device
  volume through the conference object.
  This will ensure that whatever type of confenrece is and regardless if the
  device is hosting or being a participant, the application will have only
  one interface to use and the SDK will work under the hood.

Deprecated methods:
  Delete linphone_core_mute_mic and linphone_core_is_mic_muted
  Add LINPHONE_DEPRECATED to deprecated Account parameter methods

Tester:
  Pass conference factory uri to ClientConference constructor instead of
  focus identity

Memory leaks:
  Free data of list returned by linphone_friend_get_phone_numbers

the remote contact address if not null when the call state is
StreamRunning or Paused and the conference is in state Created or
CreationPending

Add "LeaksMemory" to "Core restarts as soon as chat room is created"

Adapt video call quality tests to take into account changes in network simulator and available bandwidth estimator.
Fix initialization of NatPolicy that could be left orphaned in case of remote provisionning with default_values.

ChatMessagePrivate::setParticipantState and
ChatMessagePrivate::setState.

All event regarding a chat message will now chat the state of a
participant and then if neecesary the state of the chat message will
follow.

For IMDN controlled stats (i.e. DeliveredToUser, NotDelivered and
Displayed), the state of the chat message will be deduced based on the
states of all participants

For non-IMDN controlled states, the state of the chat message will
follow the state of the me of the chat room the message it associated
with

when initiating a call;
- from header
- account
These 2 parameters are dependent from each other which makes tricky for
the core to know exactly which account to use and the correct from
address.
In most scenarios, the from address is the account's identity address
but it is not always the case such as in the case of a direct call.
Moreover, the account cannot be always deduced in a straightforward
matter such as if the core has no default account (but it is registered
with one or more accounts) and the call parameters have not set one.

The algorithm for choosing an account is the following:
1) search in the call parameters
2) get the default account
3) look up for the best guessed account based on the from (if known) or
   to address

The algorithm for known the from address is the following:
1) look for the from header in the call parameters
2) look up for the identity address of the account (if known)
3) get the core primary account

Set Ik SDP attribute based on the account used for a call

Use account set in the call parameters before retrieving the NAT policy.
It may happen that a call session is buuild without passing an account
and in such a case, the SDK will do its best to get one

- Speaker -> participant has been added by an admin through a REFER
          -> participant has called the conference and all other participants are speakers
- Listener -> participant has called the conference and there is at least a listener being part of the conference

Look if there is a conference info matching the to address in the database in order to know if a call will be part of a conference even if the call cannot be started right away if ICE candidates have to be gathered firt

Wait for the call to onFullStateReceived before updating the conference informations when parsing a NOTIFY full state. This allows to optimize database accesses

Fix an audio issue happening after disconnection of a bluetooth headset, on Mac. Implement automatic reloading of audio devices.

  - Add callback to notify the application that a participant has changed role in the conference
  - Take into account role when creating the list of participant informations of a conference
  - Give priority to the conference information stored in the database over that cached in the call log object
  - When a participant is added, give the application a pointer to it with all the informations up to date
  - In the event of a full state, reduce the number of database accesses by updating the conference information in the callback onFullStateReceived. Previously, for every participant added a DB access was required in order to update the conference information

Tests:
  - Add verification of role and sequence id of every participant info in the conference information in the call logs and conference information
  - add helper functions to ease checking of conference informations

Compared to release/5.2, the fix had to be re-worked.

This is based on bctoolbox log tags feature.
Rework Alert API for consistency.