[bisq-network/bisq] Wrong popup message about trade limits (#3885)

[Pac]

### Description

When a user tries to take an offer which is above his trade limits, the popup message says that he needs to wait 2 months.

But it is not the case anymore, since account signing was implemented.

![image](https://user-images.githubusercontent.com/6444444/72171240-5ebe9e00-33b1-11ea-80f4-a6be02a920c3.png)


#### Version

1.2.5

### Steps to reproduce

Create an unsigned account and try to take an offer above its limit.

### Expected behaviour

The message should say whether the account is signed or not and how long ago it happened.
There is a similar generic message in popup.warning.tradeLimitDueAccountAgeRestriction.buyer
But I think we could make it better, showing the user data.

Something like:
The payment method for this offer is considered risky for bank chargebacks.
Your allowed trade amount is limited because of these security restrictions.
With this version of the software, trading peers can verify and sign each others' payment accounts to create a network of trusted payment accounts.
After successfully trading with a peer with a verified payment account, your payment account will be signed and trading limits will be lifted after 30 days.
For more information on account signing, please see the documentation at https://docs.bisq.network/payment-methods#account-signing.

`Your account has not been signed.`
[or]
`Your account was signed XXX days ago (your limit will be lifted in (30-XXX) days).`

Your trade limit is not sufficient for that offer. You cannot take that offer at the moment.
`Your trade limit is: XXX.`
`The minimum trade amount of the offer is: XXX.`


### Actual behaviour

See message on the screenshot above.


#### Additional info

This could be easily fixed with minor changes to the strings file or the offerbookview file.
But I think that a message with more data like above would be better, which is more complex than my limited java abilities allow me to fix.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/3885
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200110/9b8ddfb8/attachment.html>