feat: add scanned height

[SWvheerden]

Description

adds a callback to the FFI to get access to the height the wallet scanned blocks to
Adds a UI display to console wallet to view the displayed height

Motivation and Context

Just showing the tip height of the block chain does not have that high a meaning, its the scanned height that's important an we should show this.

How Has This Been Tested?

Manual + unit tests

[github-actions]

Test Results (CI)

    3 files    114 suites   40m 57s ⏱️
1 296 tests 1 295 ✅ 0 💤 1 ❌
3 697 runs  3 696 ✅ 0 💤 1 ❌

For more details on these failures, see this check.

Results for commit f56d9de.

♻️ This comment has been updated with latest results.

[github-actions]

Test Results (Integration tests)

 2 files   1 errors  9 suites   11m 9s ⏱️
19 tests 18 ✅ 0 💤 1 ❌
21 runs  18 ✅ 0 💤 3 ❌

For more details on these parsing errors and failures, see this check.

Results for commit f56d9de.

[brianp]

How often is the known tip, and scanned height different? I'd usually expect the scanned height to catch up fairly fast. What's the use case / reason we're building for here?

[SWvheerden]

Fairly ofter actually.
If you watch your wallet when mining, it take a few seconds to scan the new mined height, although the base_node already shows height mined.

You see the behavior in when the height shown is at tip, but you don't see your coinbase yet.

Also when you stop and start the wallet, which is a big thing for mobile. It becomes a big issue.