[0.5] Update account history object sorting logic

[abitmore]

Describe the bug
Current code for sorting account history object will be obsolete after bitshares/bitshares-core#1675 is done.

bitshares-ui/app/components/Account/RecentTransactions.jsx

Lines 22 to 28 in 83edcc3

	function compareOps(b, a) {
	if (a.block_num === b.block_num) {
	return a.virtual_op - b.virtual_op;
	} else {
	return a.block_num - b.block_num;
	}
	}

The correct logic is to compare all the 4 fields (block_num, trx_in_block, op_in_trx, virtual_op) in the object (it is also correct before bitshares/bitshares-core#1675 is done).

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[alexandr-masl]

hi everyone, can I take this one.
thanks in advance.

[startailcoon]

@alexandr-masl, @sschiessl-bcp already has this claimed and fixed.

The changes mentioned will be live in version 3.1.0, Testnet relase 16 April, and main network release 30 April.

Make sure to check if it's required to keep backwards compatibility.

[sschiessl-bcp]

There is already a PR for this one in our repo, will be forwarded after RC is done