fix(datastore): improve performances on messages store

[riccardomodanese]

Brief description of the PR.
This pr introduces a parameter to tune the datastore driver behaviour on message storing.

Related Issue
none

Description of the solution adopted
A new parameter allows to set the type of check the datastore does about the message uniqueness on message storing.

• NONE no checks are made
• BOUND check is made only in the index of the account where the message should be stored based on the current indexing policy
• FULL check is made in all the indices of the account (current and default)

Depepending on the use case this parameter enhance the flexibility.

Screenshots
none

Any side note on the changes made
none (the default value for this parameter let the datastore to work as before so no changes in the datastore behaviour using the default value

[codecov]

Codecov Report

Merging #3915 (c5eb2b0) into develop (5c0ea6c) will increase coverage by 0.10%.
Report is 8 commits behind head on develop.
The diff coverage is 0.00%.

Additional details and impacted files

@@              Coverage Diff              @@
##             develop    #3915      +/-   ##
=============================================
+ Coverage      20.51%   20.62%   +0.10%     
  Complexity         6        6              
=============================================
  Files           1945     1946       +1     
  Lines          41660    41697      +37     
  Branches        3946     3951       +5     
=============================================
+ Hits            8548     8598      +50     
+ Misses         32715    32700      -15     
- Partials         397      399       +2     

Files	Coverage Δ
...tastore/internal/model/MessageUniquenessCheck.java	0.00% <0.00%> (ø)
...e/internal/mediator/MessageStoreConfiguration.java	38.46% <0.00%> (-4.10%)	⬇️
...service/datastore/internal/MessageStoreFacade.java	0.00% <0.00%> (ø)

... and 9 files with indirect coverage changes